Repeated glb file updates in resources cause materials to be assigned incorrectly

Release Type: Official Release/GitHub (please choose appropriate option)
stride 4.4 beta 5
Version: Version number and/or git branch

Platform(s): Does the problem occur on Windows, Android...?

Describe the bug
A clear and concise description of what the bug is.

After a few edits to a resource glb file it will cause materials to be assigned incorrectly, seems to be related to the number of materials in a file

To Reproduce
Steps to reproduce the behavior:

1. Using stride 4.4 beta 5 create a fps template project
2. import \1\v1.glb into the project and drag it into the scene
3. notice it appears correct
4. replace the resource file with \2\v1.glb and refresh the scene
5. notice it appears correct
6. replace the resource file with \1\v1.glb and refresh the scene
7. the last cube will have an incorrect material assigned.

Expected behavior
A clear and concise description of what you expected to happen.

I would expect the materials to be assigned correctly

minrepro.zip

Screenshots
If applicable, add screenshots to help explain your problem (use GitHub drag & drop)

Log and callstacks
If any, please attach here any log or callstack (preferably in a .txt file using GitHub drag and drop)

Additional context
Add any other context about the problem here.

Start by opening the attached minrepro.zip and reproducing the sequence in a Stride 4.4 beta 5 FPS template: import the two v1.glb files, refresh the scene after each replacement, and compare the materials. The work is done when repeated replacements leave every cube with its correct material.