[release/1.3.1] [CO-354] Implement NetworkMagic logic

[mhuesch]

Description

This PR/commit implements part (4) of our plan.

We pipe the full NetworkMagic to the "frontier" outlined above. This means bridging the gap from where we have ProtocolMagic to where we need NetworkMagic (and had NMMustBeNothing hardcoded).

Since PR #3559 splits the test-suites, we see most of the changes in this PR are to source-code files.

Linked issue

https://iohk.myjetbrains.com/youtrack/issue/CO-354

Type of change

• [~] 🐞 Bug fix (non-breaking change which fixes an issue)
• 🛠 New feature (non-breaking change which adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
• [~] 🏭 Refactoring that does not change existing functionality but does improve things like code readability, structure etc
• [~] 🔨 New or improved tests for existing code
• [~] ⛑ git-flow chore (backport, hotfix, etc)
  ^ this PR adds the capability for differently formatted Addresses, which include a NetworkMagic value. Thus it is a breaking change for testnets (NMJust), but backwards compatible for mainnet/staging (NMNothing).

Developer checklist

• I have read the style guide document, and my code follows the code style of this project.
• If my code deals with exceptions, it follows the guidelines.
• I have updated any documentation accordingly, if needed. Documentation changes can be reflected in opening a PR on cardanodocs.com, amending the inline Haddock comments, any relevant README file or one of the document listed in the docs directory.
• [~] CHANGELOG entry has been added and is linked to the correct PR on GitHub.
  ^ there is no 1.3.1 section in the CHANGELOG, and this is dev work on a release branch, so I'm skipping this.

Testing checklist

• [~] I have added tests to cover my changes.
• All new and existing tests passed.
  ^ tests we added/modified in [release/1.3.1] [CO-354] Split test-suites for NMNothing/NMJust #3559 - we are relying on those.

[mhuesch]

N.B. this PR contains commits which are part of PR #3556, PR #3558, and PR #3559. Thus, the "Files Changed" is inflated, and if someone reviews this before #3556 / #3558 / #3559 are merged, it would be simplest to review only the commit:

f3f87824f9 [CO-354] Implement `NetworkMagic` logic

(hashes might change if we force-push)

EDIT:
I, @intricate, have rebased this branch on release/1.3.1 after the merging of #3556, #3558, and #3559 so this comment no longer applies.

[erikd]

LGTM! Looks like a lot of very tedious work to get to this stage.

[disassembler]

You need to change the asset locked wallet and address in wallet integration test:

$ git grep Ae2tdPwUPEZ5YjF9WuDoWfCZLPQ56MdQC6CZa2VKwMVRVqBBfTLPNcPvET4
wallet-new/integration/Util.hs:    WalletId "Ae2tdPwUPEZ5YjF9WuDoWfCZLPQ56MdQC6CZa2VKwMVRVqBBfTLPNcPvET4"

$ git grep DdzFFzCqrhswMWoTiWaqXUDZJuYUx63qB6Aq8rbVbhFbc8NWqhpZkC7Lhn5eVA7kWf4JwKvJ9PqQF78AewMCzDZLabkzm99rFzpNDKp5
scripts/test/wallet/integration/default.nix:    assetLockAddresses = [ "DdzFFzCqrhswMWoTiWaqXUDZJuYUx63qB6Aq8rbVbhFbc8NWqhpZkC7Lhn5eVA7kWf4JwKvJ9PqQF78AewMCzDZLabkzm9>

You'll need to spin up a demo cluster with this PR, grab any of the genesis wallets that are imported (e.g. "2cWKMJemoBakxGHgy85BN6JJooy54EmWxCoobAXe3NRfyEbuMnJAZSr5oAzD5F5aoodRD") and find the address in that wallet. Then update both of the above files with the wallet Id and the blacklisted address in that wallet.

Addressed this particular issue.