fix: NetworkTransform synchronization fixes and owner authoritative performance improvement on server-host [MTT-6971]

[NoelStephensUnity]

This PR address the following issues:

• When an owner authoritative client uses half precision with position synchronization, it was possible for the server-host to forward the owner's state updates with already processed NetworkDeltaPosition values.
  • This could cause visual anomalies on non-authoritative remote clients during the collapsing of the position delta into the total local position.
• Due to the non-guaranteed spawn order of NetworkObjects, scale synchronization could potentially not synchronize properly if the child NetworkObject had not yet been parented.
  • Now NetworkTransform will send both local and lossy scale values if scale synchronization is enabled during teleporting and/or the initial synchronization and the NetworkObject is parented. The receiver determines which to apply based on whether the receiver's instance is parented yet (or not) and whether world position stays was used when the NetworkObject was parented.
• NetworkTransform no longer uses NetworkVariables for updating transform state due to the processing cost when updating owner write permission NetworkVariables on the server-host.
  • The NetworkVariable serialization cost of owner authoritative NetworkTransforms was:
    • The deserialization on the server-host side at the beginning of the frame
    • The re-serialization cost for each connected client at the end of the frame
  • With the switch over to named messages, the serialization cost of owner authoritative NetworkTransforms is now:
    • The deserialization on the server-host side at the beginning of the frame
      • The named message payload is forwarded just prior to the host deserializing.

MTT-7057
MTT-7056
MTT-6971

fix: #2628
fix: #2639

Changelog

• Fixed: Issue with client synchronization of position when using half precision and the delta position reaches the maximum value and is collapsed on the host prior to being forwarded to the non-owner clients.
• Fixed: Issue with scale not synchronizing properly depending upon the spawn order of NetworkObjects.
• Fixed: Issue position was not properly transitioning between ownership changes with an owner authoritative NetworkTransform.
• Fixed: Issue where a late joining non-owner client could update an owner authoritative NetworkTransform if ownership changed without any updates to position prior to the non-owner client joining.

Testing and Documentation

• Includes new and updated integration tests.
• No documentation changes or additions were necessary.