Fix Set Kinematic When Not Authoritative not being applied correctly.

[jamiebrynes7]

Description

We had two different bugs that revealed themselves when we removed the AuthorityLossImminent state in #1451

• The SetKinematicFromAuthoritySystem was grabbing the first authority change received in that frame to use as the authority change. In the case where you got AuthorityLossImminent and then NotAuthoritative in the same frame, it would grab AuthorityLossImminent (incorrectly).
• The query returned by ConstructEntityQueryDesc<T> would have an Exclude<TransformInternal.HasAuthority> filter on it. This meant that we would never even attempt to reset the kinematic authority set when you become 'not authoritative'.

These two bugs combined meant that the kinematic state would never be by the system ever. In the playground, this seemed not to matter so we never noticed it (and the fact that we typically would only ever run with 1 worker locally).

When we removed the AuthorityLossImminent state, the first bug ceased to apply meaning that we just ended up with weird behaviour with multiple GameLogic workers.

This PR fixes both these bugs, the first by grabbing the correct element from the authority changes span and the second by making ConstructEntityQueryDesc take a tri-state enum of either (Exclude, Ignore, or Required).

Remaining work

• Cubes are now being shot across the world and I'm not entirely sure why..
• Changelog

Tests

• Ran locally with two workers and ensured that the Is Kinematic state was being set.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

0.0% Coverage
0.0% Duplication