Convert Web3Accessor -> ChainSafe with usability features

[rob1997]

Summary
Currently we on use Web3Acessor for fetching Web3 instance instead it can be converted into a ChainSafe singleton object that can handle connection, disconnection, signing and sending transactions.

Suggested features or ways to address the summary
ChainSafe should be a singleton class with Connect, Disconnect, Sign and Send Transaction methods.

Motivation
This will improve usability for devs greatly

Acceptance Criteria
Devs can connect, disconnect, sign and send transaction from ChainSafe.cs
Devs can immediately use read blockchain features that don't require signing, like reading things from the chain.

Blockers
(OPTIONAL) [Do you see any blocker that needs to be done before implementing this feature?]

Dependencies
(OPTIONAL) [Do you know about dependencies that directly affect this issue?]

Additional Context
(OPTIONAL) [Add any other context, files, images (screenshots/videos), diagrams, or documents about the feature request here.]

Final Steps

• Give it one of these labels Type: Feature Type: Enhancement
• Add your estimation

Estimations

Story Point	Amount of effort	Amount of time	Task Complexity	Task Risk or Uncerntainty
5	Moderate efort	A few days	Mediium complexity	Moderate

[rob1997]

@kantagara anything you would like to add?

[rob1997]

Single Scene System
Read-only operations