chore: Update Silk.Net.Assimp from 2.22.0 to 2.23.0

[w0wca7a]

PR Details

Fixes bone twisting artifacts on animations.

This change adapts the fix described in Silk.NET PR #2489 and applies the same approach within Stride's animation system.

Related Issue

#3116

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[Eideren]

Note that afair silk.net packages must be updated in lockstep; other silk packages should be updated to match this new version

[VaclavElias]

These if not more in Directory.Packages.props?

[w0wca7a]

I'm not sure about other packages since I didn't check them. I need time to understand how stable they work.

[Kryptos-FR]

Note that afair silk.net packages must be updated in lockstep; other silk packages should be updated to match this new version

Would it make sense to introduce a property (e.g. SilkVersion) and reuse it in all related packages? That way one line change would be necessary and it clearly conveys that they should be updated together.

I'm doing something similar for the AvaloniaVersion in the xplat-editor branch.

[w0wca7a]

Would it make sense to introduce a property (e.g. SilkVersion) and reuse it in all related packages? That way one line change would be necessary and it clearly conveys that they should be updated together.

Overall, isn’t bad idea. But if a user ever needs to update/downgrade just one library, for example, Silk.Net.Assimp, since Silk.Net is a huge collection of separate packages covering rendering, input, import, VR, etc.?