Create `surfnet_blockAccountDownload` cheatcode

[MicaiahReid]

When you have deployed a program to mainnet and initialized accounts, your local surfnet automatically pulling these accounts can be problematic - now the accounts you're wantint to test initialized are already being pulled from mainnet initialized.

We need a cheatcode to block an account from being pulled from mainnet, including the accounts it owns.

Wire format would be:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "surfnet_blockAccountDownload",
  "params": [
    "<my_program_id>",
    {
      "includeOwnedAccounts": true
    }
  ]
}

[MicaiahReid]

@lgalabru, I'd love an opinion on the naming and wire format for the cheatcode, you're good at that

[lgalabru]

hmm, good one. feels like the contract (inputs / outputs) should be consistent with surfnet_streamAccount - it's basically doing the opposite.

• surfnet_isolateAccount
• surfnet_freezeAccount
• surfnet_quarantineAccount
• surfnet_pinAccount
• ?

[MicaiahReid]

Agreed on being consistent. My initial thought was surfnet_blockAccountStreaming was my original, but it's not quite clear if it's blocking all accounts, and disabling an account from being downloaded isn't equivalent to the streaming.

I'm not sure if any of those suggestions are clear enough to what it's doing. My favorite of them might be pin account

What about surfnet_offlineAccount, surfnet_localAccount, surfnet_localizeAccount, surfnet_detachAccount?

I may be liking surfnet_localizeAccount 🤔

[CanardMandarin]

Hi! I made a PR for this issue, let me know which naming you’d like to go with.
I personally feel that surfnet_offlineAccount or surfnet_excludeAccount are more explicit.