Consistent Signals: MultiplayerAPI, MultiplayerPeer, WebSocketServer, WebSocketClient

[comods]

Similar networking APIs have been added with inconsistent names.

My reasoning for consistency (weighed against each other): Reduced confusion (what timing? differentiated verb), consistent implied details (started what? cognitive load), cleaner reusable code (can: n in variant group: n.enabled = true), ease of knowing more features (A == B, A or B needed?), reduced double negatives, and reduced typing.

The networking category (includes MultiplayerAPI, MultiplayerPeer, WebSocketServer, WebSocketClient) is full of API naming Outliers.

This Proposal is for the category to be consistent within itself, for the above reasons.

[comods]

Rename AA:

AA is for disconnected.

connection_failed (All use connection_failed except WebSocketClient uses connection_error)
server_disconnected (All use *_disconnected except WebSocketClient uses *_closed)
*_connected (WebSocketServer/MultiplayerPeer use *_connected) (MultiplayerAPI uses *_connected & connected_to_*)
(MultiplayerPeer uses *_connected & *_succeeded) (WebSocketClient uses *_established)
server_connected (from connection_succeeded & connection_established)