Network Segregation

[amydevs]

Description

This PR aims to implement network segregation via a fractal network pattern enforced through token verification,

Issues Fixed

• Fixes Network Segregation/Authentication Token Logic #779
• REF ENG-370

Tasks

• 1. Implement Token Verification Logic into RPC system

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[tegefaulkes]

@amydevs avoid wip commits. Be sure to add a description to them wip: did a thing just so we can get an idea of the changes from the commit message. On top of that, if you know CI wont pass then add [ci skip] in the commit message as well.

The PR description needs to be updated as well since we've subdivided the work. This is focusing solely on the authentication logic for the network access claims now. So the description and tasks need to reflect that.

[linear]

ENG-370 Network Segregation/Authentication Token Logic

[linear]

ENG-373 Adding authentication stage logic to `NodeConnection`

[amydevs]

I've added the authentication logic + tests, i'm going to look as to where to slot in the logic that will prevent calls being made to the RPC client when the connection has not yet been authenticated, as well as where to drop the connection if authentication fails.

[CMCDragonkai]

Merge this with just mainnet and testnet segregation.

Start with --network=X use the X is the unique identifier for the network. Then just use 1 single token the ClaimNetworkAccess token to indicate what network you're claiming to access to.

Special case for --network='' which is an empty string. You could claim with an empty string as the unique identifier, or we can say it's just equivalent to null or undefined meaning there's no token at all.

Separate out the work for PKE. PKE side of things can be done later.