The Inspector rounds up float values up to a maximum of 7 digits and overwrites the actual values in the file when saving the asset

Reproduction steps:
1. Open the attached “2088735ListBug“ project (link in the internal comments)
2. In the Project window, right-click on the “TestData” folder > “Create” > “Animal Sequence Data”
3. Enter Play mode
4. Wait until a “NewAnimalSequence” folder is created in the “TestData” folder
5. Exit Play mode
6. From the Windows File Explorer, open one of the “TestAsset_[…].asset” assets created in the “NewAnimalSequence” folder with a code/text editor of your choice
7. Look for the “spawnPoint” and “waypoints” coordinates' values that have >7 digits
8. In the Project window (Unity Editor), select the same .asset file and find those same values in the Inspector
9. Notice that those values in the Inspector have decreased precision (they are rounded to a maximum of 7 digits in total) when compared to what is displayed in the code/text editor of choice
10. Left-click on any of those values in the Inspector (you can deselect them afterwards and there is no need to press the Enter key)
11. Save the asset by pressing Crtl+S or by going to the “File” menu and pressing “Save” or ”Save Project”
12. Observe the same values displayed in the code/text editor of choice

Expected result: The asset’s values remain unchanged
Actual result: The asset’s values (only the touched ones) have been overwritten to their rounded versions that the Inspector is displaying

Reproducible with: 2022.3.61f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7

Reproduced on: Windows 10, Windows 11 Pro (23H2)
Not reproduced on: No other environment tested

Notes:

• Could not test in a new project (due to the custom tools in use)
• You can delete everything in the “TestData” folder to restart the test
• When testing the issue at first, the Inspector used to overwrite the entire asset file when saving (even the values that have not been touched) but afterwards, such behavior has changed to only overwriting the touched values and we were unable to bring the old behavior back
• This issue is causing a lot of hassle for the customer with VCS commits because of the ever-changing values that were not intended to be changed