fix: NetworkAnimator does not allow disabling or enabling parameters for synch

[NoelStephensUnity]

Purpose of this PR

This PR addresses the primary issue of NetworkAnimator not providing a way to exclude specific parameters from synchronization to provide users the ability to handle the synchronization of the excluded parameters themselves or to handle them via a calculation performed on non-authority instances.

This PR also includes:

• Updates to NetworkAnimator's inspector view where you can now select a server or owner authoritative model via drop down as opposed to having to override the class.

(Above, there is now an "Authority Mode" field and a list of the Animator's parameters that can be enabled or disabled for NetworkAnimator synchronization)

Jira ticket:

MTTB-1485

fix: #3530

Changelog

• Added: NetworkAnimator.AuthorityMode which allows you to select whether the NetworkAnimator will use a server or owner authority model for state updates (like NetworkTransform).
• Added: The ability to select which Animator parameters the NetworkAnimator should synchronize. This can be done via the inspector view interface or during runtime via NetworkAnimator.EnableParameterSynchronization.
• Changed: NetworkAnimator to use the RpcAttribute along with the appropriate SendTo parameter.
• Fixed: Issue with authority animator instance sending itself RPCs.

Documentation

• Includes integration tests.
• Includes documentation updates. (WIP)

Testing & QA

Functional Testing

Manual testing :

• Manual testing done
  • Used test project.
  • Used the MTTB-1485-Replication project:
    • MTTB-1485-Replication.zip

MTTB-1485-Replication Project

Verifying the fix

• Open the project
• Create one MPPM virtual client.
• Enter into play mode.
  • Start a DAHost within the editor.
  • Connect a client via the virtual client.
• If not already running, start the profiler and enable NGO Messages and NGO Objects.
  • Under NGO Objects, disable everything but the outbound RPCs.
• Move around the DAHost player a bit.
  • Note: No RPCs should be sent while walking or running around.

Replicating the underlying issue

• In the same running instance, make sure the editor Game view is in focus and then hit the [Enter] or [Return] key.
  • You should see a runtime message and console message stating the speed is being synchronized.
• Move the DAHost player around some more.
  • Note: RPCs are sent (almost) continuously while moving around.

Automated tests:

• Covered by existing automated tests
• Covered by new automated tests

Does the change require QA team to:

• Review automated tests?
• Execute manual tests?

If any boxes above are checked, please add QA as a PR reviewer.

Backports

No backport is needed as this sustainability update will only be available in v2.x.

[EmandM]

Yay for this update! This is huge!

[noellie-velez]

Looks good to me! 🚀

[jabbacakes]

I've pushed a commit with a general spit and polish of the page (I don't think I've ever had a chance to look at it before), so there are a lot of general changes not limited to the new content. Nothing major tho, just tidying up.

@NoelStephensUnity only real change you might want to look at is in the 'Selecting the authority mode' section. I reworked this one to remove mention of before and after/earlier versions of NGO. Instead it presents the drop-down option first and then says FYI you can do it the old way too.