fix: client owned NetworkObject with prefabhandler destroy order incorrect on host-server side

[NoelStephensUnity]

Replication of the issue is as follows:

• Using a client-server network topology
  • At least one client must be connected to a host or server.
• NetworkObjects are spawned with:
  • Ownership belonging to a connected client.
    • Does not occur if they are owned by the server.
  • Don't destroy with owner is not enabled (i.e. it will destroy when the client leaves)
    • Does not occur if don't destroy with owner is enabled.
• While the NetworkObjects (owned by the client) are still spawned, the client disconnects.

NGO v2: On the host/server side, this will cause the destroy method to be invoked twice.
Backport to v1: #3202

fix: #3190

Changelog

Fixed: Issue where a spawned NetworkObject that was registered with a prefab handler and owned by a client would invoke destroy more than once on the host-server side if the client disconnected while the NetworkObject was still spawned.

Testing and Documentation

• Includes updates to NetworkPrefabOverrideTests.
• No documentation changes or additions were necessary.