NetworkTransformReliable is buggy when assigning/releasing client authority

[vodolazov]

Describe the bug
Assign and release client authority causes NetworkTransformReliable to flicker and leave object transform out of sync. Not sure about SERVER-CLIENT config, but the bug is prominent in HOST-CLIENT config.

[IMPORTANT] How can we reproduce the issue, step by step:
Please tell us how to reproduce your issue, STEP BY STEP, with one of our built in examples.
-> Run HOST and connect CLIENT to the HOST
-> On HOST assign client authority to and object
-> BUG!!! On CLIENT the object flickers - momentarily jumps to a weird place and comes back
-> Move the object on HOST
-> Transform is in sync on CLIENT
-> Release authority on HOST
-> BUG!!! The onbject flickers again on CLIENT

Another sceneario:
-> On CLIENT -> assign authority and start updating transform
-> On HOST the object is in sync
-> On CLIENT release authority
-> BUG!!! On CLIENT the object jumps to a random location. This is not deterministic, but happens very often

This problem makes NetworkTransformReliable pretty useless in HOST-CLIENT config where authority used to manipulate objects transforms from client side.

The bug can be addressed by changing NetworkTransformReliable to NetworkTransformUnreliable, which works as expected.

Expected behavior
Setting client authority must enable transform propagation from client to server without going out of sync randomly.

Desktop (please complete the following information):

• OS: Windows
• Build target: UWP
• Unity version: 2022.3
• Mirror branch: 89.8.0

Additional context
I think the bug is present is HOST-CLIENT config. SERVER-CLIENT config is likely not affected.

[vodolazov]

This might be related to #3959. I outlined the fix there

[vodolazov]

[ServerCallback]
void OnClientAuthorityChanged(NetworkConnectionToClient conn, NetworkIdentity identity, bool authorityState)
{
if (identity != netIdentity) return;

// If server gets authority or syncdirection is server to client,
// we don't reset buffers.
// This is because if syncdirection is S to C, we will never have
// snapshot issues since there is only ever 1 source.

if (syncDirection == SyncDirection.ClientToServer)
{
    if (!isClient)
        ResetState();
    RpcResetState();
}

}
Prevents executing ResetState() twice on the host.