Fix resolve errors when networking EntityUids referencing deleted entities

[slarticodefast]

Another approach to the problem explained in #6152

This basically just disables the resolve error log. The component state is properly generated and networked regardless. If the referenced entity is deleted then GetNetEntity will return an invalid NetEntity which in turn is converted to an invalid EntityUid on the client, meaning that the server and client component state are the same after networking.

For testing:

• Spawn a jukebox
• Play a song and let it finish so that the audio entity gets deleted
• Use the dirty console command to dirty the jukebox entity, which will network the reference to the deleted audio stream

Ideally this would be fixed with either WeakEntityReference or a relations system that automatically sets the datafields back to null when the entity is deleted. But this is causing an absolutely insane amount of over 24000 errors each day, which drowns out all other errors to the point that they become unusable and even cause lag spikes on the server. We even did not notice that admin logs were failing to save to the database for 2 weeks because no one saw the errors. And the discord relay notfying us about error spikes is constantly spamming us despite us adjusting the sensitivity multiple times, so no one even looks at it.

All PRs so far have been closed and I don't expect a new WeakEntityReference or relations system implementation any time soon, so I think this is a reasonable solution for the meantime to stop the error spam.

[PJB3005]

This is just silencing an error. We don't want this.