GameClock RPCs don't set SenderRpcId + Remove config settings to disable GameClock/Synchronizer

[DoubleDeez]

I have an RPC I call with this.MDRpc(), but in the body of the RPC, when I call GetTree().GetRpcSenderId(), the result is 0 when it should be the ID of the original sender.

[DoubleDeez]

@Beider I don't know if it's possible to set the sender id in the tree, but otherwise we'll need some sort of alternative.

[Beider]

Add an MDGetRPcSenderId()?

[DoubleDeez]

Yeah, looks like Godot's is read-only so we'll have to

[Beider]

For non-game clock this is easy enough we can just set the sender value right before we call. For game clock values we have to store the sender id, we already got a custom class to store data for game clock calls so this shouldn't be too hard either.

[Beider]

This expands the scope of this issue, but it has been decided that GameClock and GameSynchronizer should always be on. Might as well fix that in the scope of this issue. This involves:

• Remove all configuration settings related to turning off these features (includes from config files as well as virtual methods)
• Update all the places where we check if GameClock or GameSynchronizer == null (MDRpc, MDRset, MDReplicator, MDReplicatedMember, etc..)
• Finally add this MDGetRpcSenderId() which can just be stored into the object that is created when ClockedCall is received in the MDReplicator. Then set it right before the Invoke() and add a method to get it to node extensions.