Separate chainAdapterReady from chainModuleReady.

[jnaviask]

Description

We use a global Subject called "app.chainReady" in dynamic components to wait until the entire chain has initialized before loading additional dynamic data.

This Subject was also being used in the SubstrateAccounts module to handle deferred initialization of the "ChainInfo" module, i.e. the SubstrateChain class. However, the app.chainReady waits for the entire chain adapter to load, not just the app.chain.chain module.

To fix this, I separated it into two different Subjects: app.chainAdapterReady (same as original app.chainReady), and app.chainModuleReady (used in Accounts and possibly other future modules to defer initialization).

Motivation and Context

This bug was causing loading errors on production: the app.chainReady wouldn't load until the SubstrateCollective module loaded, but the SubstrateCollective module assumes that account deferred initializations have already resolved (i.e. that the app.chainModuleReady has resolved), so it finds itself unable to query for balances and throws an error.

How Has This Been Tested?

Reproduced bug in dev environment, verified fix.

Types of changes

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• My change should be included in the release notes.
• I have updated the documentation accordingly.
• I have linted the code locally prior to submission.

[drewstone]

Looks good, we can def cut down on some redundancy here