Feeling kinda documenting, might delete later.

The 0x API's are generally of a higher engineering quality. The exceptions encapsulate the error cases better, and they also manage the Ledger Transport lifecycle, which was a flaw of the previous implementation. We use them in keep-core too.

We use @0x/subproviders for the Ledger/Trezor integration.

@ledgerhq/hw-app-eth is being upgraded as an older version was installed by accident.

"Stolen" from the Compound dApp. We'll leave these here as a placeholder, until we get the real UX in.

This introduces a custom LedgerSubprovider, which mitigates the existing 0x LedgerSubprovider's failure to produce the correct transaction signature values.

Colocate connector with other wallet info

We don't need this anymore - it was only supported by InjectedConnector and didn't appear to be useful for our case anyways.

This is simpler and a bit more efficient.

…-ledger

There's a known issue that Trezor's API will throw for larger network ID's. Next commit should fix that.

Much like our Ledger subprovider, this provider mitigates issues with the Trezor subprovider provided by 0x - namely, chainId's < 255 are not supported.

The `AbstractConnector` returns only first account by default. With our
custom implementation of `TrezorConnector` allows users to get eg. 15
accounts and sotres the selected account. The `TrezorConnector`
overrides a `getAccount` fn from the `AbstractConnector`, and this
function returns a selected account instead of the first account.

The ChooseAccount component allows user to choose a any address from the
hardware wallet.

Extracted the components from the `ConnectWalletDialog` component into separate
functional components.

Pass a number of accounts arg to the `getAccounts` fn in the trezor
provider and set to default value (15).

Removed unused variables, used a common functions.

Simplify default assignment and use specific type for
param in jsdoc

Add Trezor wallet connector