[Morse->Shannon Migration] feat: implement MsgClaimMorseSupplier handler

[bryanchriswhite]

Summary

Implement MsgClaimMorseSupplier message handler.

Changes:

• Implement MsgClaimMorseSupplier handler
• Update MsgClaimMorseSupplier and MsgClaimMorseSupplierResponse types
• Add EventMorseSupplierClaimed event
• Add app-integration tests
• Add module (msgServer/keeper) tests

Issue

• Issue: [Morse->Shannon Migration] Migration module #1034

Type of change

Select one or more from the following:

• New feature, functionality or library
• Consensus breaking; add the consensus-breaking label if so. See [Infra] Automatically add the consensus-breaking label #791 for details
• Bug fix
• Code health or cleanup
• Documentation
• Other (specify)

Sanity Checklist

• I have updated the GitHub Issue assignees, reviewers, labels, project, iteration and milestone
• For docs, I have run make docusaurus_start
• For code, I have run make go_develop_and_test and make test_e2e
• For code, I have added the devnet-test-e2e label to run E2E tests in CI
• For configurations, I have update the documentation
• I added TODOs where applicable

[Olshansk]

@bryanchriswhite Remember how I said that we'll have new requirements along the way (because it's hard to identify everything ahead of time).

tl;dr Not blocking this PR, but this comment is likely going to be the ref to a TODO_MAINNET/TODO_UPNEXT PR.

---

Here is another curveball:

• Custodial staking: https://docs.pokt.network/community/governance/creds-governance-upgrade/onboarding-new-voters#custodial-service-providers
• Non-custodial staking: https://docs.pokt.network/community/governance/creds-governance-upgrade/onboarding-new-voters#docs-internal-guid-78ff420c-7fff-6007-28e8-bcbdc255c20c

If you run

$ pocket nodes stake

The definitions look like so (note the different output address for rewards/return of staked funds piece):

Stake the node into the network, making it available for service.

Usage:
  pocket nodes stake [command]

Available Commands:
  custodial     Stake a node in the network. Custodial stake uses the same address as operator/output for rewards/return of staked funds.
  non-custodial Stake a node in the network, non-custodial stake allows a different output address for rewards/return of staked funds. The signer may be the operator or the output address. The signer must specify the public key of the operator

If you run:

pocket query nodes --remoteCLIURL https://pocket-rpc.liquify.com >> /tmp/tmp.tx

Then this output is a list like so.

Note the address and output_address pieces.

        {
            "address": "01c6fff4e1596b5c9b5a6da1101ef2bc72ecfed4",
            "public_key": "1b92ad73f92df923e6eba9da8f0834ab02363f9ea859d66d82e0b104ac8281db",
            "jailed": false,
            "status": 2,
            "chains": [
                "F01B",
                "F016",
                "F00C",
                "F025",
                "F02E",
                "F017",
                "F032",
                "F01C"
            ],
            "service_url": "https://7690.n.poktstaking.com:443",
            "tokens": "60010000000",
            "unstaking_time": "0001-01-01T00:00:00Z",
            "output_address": "446cf0a9ad6d37b601439baf8329d163c36cbab9",
            "reward_delegators": {
                "cec3dd45e5b4a045ce9f88211ad5d2f066a81627": 35
            }
        },

As discussed previously (either explicitly or implicitly):

1. We're ignoring jailed piece for now; if this changes, I'll let you know).
2. We're ignoring reward_delegators; we simply respect/reflect the new settings only.
3. We may or may not need to take unstaking_time into account. E.g. if you're unstaking during the snapshot, we treat you as staked on Shannon; I've CCed you on a discussion in notion
4. We need to figure out output_address vs address (the whole custodial vs non-custodial piece)

The business logic I want us to add in the next PR is:

1. Rename morse_src_address and morse_signature to morse_src_owner_address and morse_src_owner_signature respectively.
2. If the output_address is empty in the morse state that's uploaded: apply the same business logic as you have in this PR (no change)
3. If the output_address is non-empty: set the owner (output) & operator (non-output) address of the Supplier in Shannon accordingly.

This is a very high-level direction but lmk if it makes sense.

[bryanchriswhite]

1. We're ignoring jailed piece for now; if this changes, I'll let you know).
2. We're ignoring reward_delegators; we simply respect/reflect the new settings only.
3. We may or may not need to take unstaking_time into account. E.g. if you're unstaking during the snapshot, we treat you as staked on Shannon; I've CCed you on a discussion in notion

👍

[bryanchriswhite]

1. Rename morse_src_address and morse_signature to morse_src_owner_address and morse_src_owner_signature respectively.
2. If the output_address is empty in the morse state that's uploaded: apply the same business logic as you have in this PR (no change)
3. If the output_address is non-empty: set the owner (output) & operator (non-output) address of the Supplier in Shannon accordingly.

👍

[Olshansk]

@bryanchriswhite Please create a GitHub Issue linking to this thread of comments as well as adding a TODO in the code linking to the github issue before merging!

[github-actions]

The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks.

You may need to run make trigger_ci to submit an empty commit that'll trigger the tests.

GCP workloads (requires changing the namespace to 1095)
Grafana network dashboard for devnet-issue-1095

[Olshansk]

Pre-ematively approcing but PTAL at this comment: #1095 (comment)