Reproduction steps:
1. Download and extract the project in "case_1316556-UnityBugHunt.zip"
2. Download P4V client from https://www.perforce.com/downloads/helix-visual-client-p4v
3. Launch P4V client, switch to Remote Server tab (if you are connecting to localhost, you will need to launch a helix core (instructions below))
4. Create a new User
5. Create a new Workspace and set the UnityBugHunt project root as the location
6. In the server Field enter "localhost:1666"
7. Click ok
8. Open the UnityBugHunt project using Unity editor
9. Go Edit -> Project Settings -> Version Control
10. Set mode to Perforce
11. Enter Username, Password, Workspace that you created in the P4V client
12. Set server to "localhost:1666"
13. Click on Connect
14. Submit all changes to the Perforce server
15. Go Window -> Asset Management -> Addressables -> Groups
16. Open the Project window
17. Go Test -> Test 4a - Addressables Reference Test
18. Go Test -> Test 4b - Addressables Reference Test
19. In the Addressable groups window, select test/AddressablesMapping/TestAsset (under ScriptTestGroup)

Expected result: The file will be selected in the Project window (check other files in Addressables groups windows)
Actual result: The file is not selected in the Project window (Note 2)

Reproducible with: 1.16.19 (2019.4.25f1, 2020.3.7f1, 2021.1.6f1), 1.17.17 (2021.2.0a15)
Could not test with 2018.4.34f1 (packages break, package manager not available)

Notes:
1. I put instructions on how to launch helix core below in edits
2. The customer described the problem in greater detail here: "Programmatically updating addresables creates reference errors.txt" (attached in Edits, but also available in the project Assets -> READMES)