feat(ClientApps)!: Client.apps signature is an array app definition

[Alex-Werner]

Issue being fixed or feature implemented

In order to handle some bugs where the same contractID were used with multiple string identifier (we set dpns by default, some users might think they want to add it too under another contract alias, which would not populate appDefinition correctly).

What was done?

• feat!: SDK Client app now take an array based options
• feat: ClientApps updated to handle multiple alias per app definition.

How Has This Been Tested?

• Added new ClientApps tests

Breaking Changes

Instead of doing previously :

new Dash.Client({
 apps: {
   "dashpay": {
        contractId: '',// Provide the dashpay contract id here
   }
 }
});

Now :

new Dash.Client({
 apps: [{
    contractId: '',// Provide the dashpay contract id here
    alias: 'dashpay'
  }]
});

Checklist:

• [X] I have performed a self-review of my own code
• [X] I have commented my code, particularly in hard-to-understand areas
• [X] I have added or updated relevant unit/integration/functional/e2e tests
• [X] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• [ ] I have assigned this pull request to a milestone

[Alex-Werner]

Fixes: https://github.com/dashevo/js-dash-sdk/issues/150

[lgtm-com[bot]]

This pull request introduces 1 alert when merging 8f590b241d439032858ed36d6a26d3de003f8797 into 4fff21849cbca7074702d85aad69cd16d9f4b30c - view on LGTM.com

new alerts:

• 1 for Unused variable, import, function or class

[lgtm-com[bot]]

This pull request introduces 1 alert when merging 3ef1a68d2dd06558866c22bf595b23028271a023 into 84761ccaba0255653c3fbd4266cce91803325f39 - view on LGTM.com

new alerts:

• 1 for Useless assignment to local variable

[shumkov]

This PR doesn't solve the problem entirely, so we need to sit and design app context logic and then implement it as one thing.