feat: ensure the injectedRegsitry opt does deep comparisons

[bee344]

Description

It allows updating the entries of the existing registry with new info~, as well as overriding existing entries~. The injected registry no longer requires to have all the fields filled when updating an existing entry, but it errors out when adding a new entry and not specifying the chain's specName or tokens.

Added updateRegistry to parseRegistry

Added the function updateRegistry to handle checking whether the entry already exists or if it's new info, and if it's already present, it updates the corresponding fields.

Added alternative interfaces with optional values

Added InjectedChainInfoRegistry , InjectedChainInfo and InjectedChainInfoKeys alternative interfaces to allow for injected registries with partial info, as well as the AssetTransferApiInjectedOpts type for comparison made AssetTransferApiOpts, ChainInfo and ChainInfoRegistry to take either InjectedChainInfoKeys or ChainInfoKeys depending on what's needed.

Updated tests and adjustedMockSystemApi

Foreign assets' tests failed because TNKR is already in the registry, so I modified the adjustedMockSystemApi's foreignAssets to another asset, updated the corresponding tests, and updated the parseRegistry's tests to account for the new functionality.

Rel: #357

[TarikGul]

On the first review I have some nits, and questions. So far though, amazing job!

[TarikGul]

As mentioned in an offline discussion we are moving this PR from a override to injection only, and a less rigid set of rules, making it as much as a deep comparison as possible

[marshacb]

lgtm!

[TarikGul]

Just one little nit, then this is good to go! Really great job :)

[TarikGul]

LGTM, really amazing job!