chore(deps): bump @metamask/network-controller from 1.0.0 to 2.0.0

[dependabot]

Bumps @metamask/network-controller from 1.0.0 to 2.0.0.

Release notes

Sourced from @​metamask/network-controller's releases.

1.9.1

Minor Changes

• Return tx errors correctly: #186
• Tests: token rates mocks: #185

1.9.0

Minor Changes

• Bump eth-contract-metadata for the maker migration: #181

1.8.2

No release notes provided.

1.8.1

Minor Changes

• Feature: speed up transaction: #172
• Feature: preferences set selected address: #178

Patches

• Bugfix: provider stop: #177

1.7.5

Patches

• Setup project for publishing from root folder: #169

Credits

Huge thanks to @​estebanmino for helping!

1.7.4

Minor Changes

• Update AddressBookController w/ consistent API: #143
• Update packages, node 10, v1.5.2: #145
• Update addressBook with entries by chainId, add isEns flag: #152
• Add EnsController: #151
• Feature: message manager: #160
• Feature: sign typed message v4: #161

Patches

• Validation and shrinkwrap: #133
• Bugfix: collectibles detection: #138
• Fix import path for AddressBookController: #144
• Update to ethereumjs-util@6: #142
• Bump node version on travisCI: #148

... (truncated)

Changelog

Sourced from @​metamask/network-controller's changelog.

[32.0.0]

Added

• Add isOutOfDate to the PhishingController, for checking whether the phishing lists are out-of-date. (#929)

Changed

• BREAKING: Make the PhishingController test synchronous (#929)
  • Rather than being polled regularly (as it was pre-v31), or updated on fetch (as in v31), the phishing lists are no longer updated automatically at all. You will need to manually call isOutOfDate to check whether they are out-of-date, and then call updatePhishingLists to update them.
• BREAKING: Migrate NetworkController to BaseControllerV2 (#903)
  • There is no more "controller configuration" with BaseControllerV2. Instead configuration is set by constructor parameters.
  • The constructor accepts a single "options" object rather than separate parameters. The initial state is now passed as part of this options object, via the state property.
  • The constructor must be passed the infuraProjectId and messenger options. The messenger should be a restricted controller messenger.
  • Controller subscriptions must be registered through the controller messenger, rather than through the controller directly.
  • A providerChange event has been added. This is dispatched when the provider instance variable is updated.
    • When there is a network switch, this is dispatched after the network has been fully initialized.
  • A new getEthQuery action has been added, for obtaining an EthQuery instance that is already setup with the current provider
    • Note that it will stop working when the provider changes, so you should call this again each time the providerChange event is dispatched.

Fixed

• Prevent parallel phishing configuration updates (#930)
• Fix issues with empty responses in ERC20Standard (#927)
  • Calling getTokenSymbol and getTokenDecimals on contracts that return empty values (0x) for symbol() and decimals() will now throw an error.

[31.2.0]

Changed

• Update phishing configuration update URL to reduce cache delay (#915)
• Update @keystonehq/metamask-airgapped-keyring from ^0.3.0 to ^0.6.1 (#913)

Fixed

• Allow Optimism & Optimism Testnet to be added via wallet_addEthereumChain (#910)
• Fix regression where a phishing configuration update network failure would cause the test method to fail (#915)
• Prevent duplicate phishing configuration update network requests (#915)

[31.1.0]

Added

• Add new error type - ApprovalRequestNotFoundError (#909)

Changed

• Replace ethers with submodules (@ethersproject/**) (#907)

Commits

• 4de13fe Release 36.0.0 (#999)
• 8e5039a Expand contributor docs (#993)
• 6777d2c Relax inter-monorepo dependencies (#998)
• f49fd49 Fix link for assets-controllers (#997)
• 55c30e2 Change naming of provider to providerConfig where applicable (#995)
• 5f1f69d Add lastFetched PhishingController state (#986)
• a3d6492 Release 35.0.0 (#990)
• bbc4327 Add commit message filter for release check (#983)
• fe822ff Export action and event handler types (#987)
• 4dbce9e Add applyPatches function to BaseControllerV2 (#980)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.