[sui-adapter] Resolve Move abort locations to package ID instead of runtime ID

[tzakian]

Description

Updates Move aborts so that the address in the abort location uses the package ID as opposed to the runtime module ID.

Basically, before if you had a package P with a module M

module P::M {
  public fun aborter() { abort 0 }
}

published at 0xA for version 1, 0xB for version 2, and 0xC for version 3, then before this change

0xA::aborter().location.address == 0xA
0xB::aborter().location.address == 0xA
0xC::aborter().location.address = 0xA

After this change

0xA::aborter().location.address == 0xA
0xB::aborter().location.address == 0xB
0xC::aborter().location.address == 0xC

The only meaningful changes are in sui-execution/latest/sui-adapter/src/error.rs the other changes are just plumbing/protocol config updates and tests.

Test plan

Added tests to make sure existing behavior is preserved, and that new behavior works as expected.

---

Release notes

Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.

For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

• Protocol: Added new protocol version (47) and enabled resolving Move abort locations to their package ID instead of runtime ID.
• Nodes (Validators and Full nodes):
• Indexer:
• JSON-RPC:
• GraphQL:
• CLI:
• Rust SDK:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sui-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 23, 2024 3:47am

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
multisig-toolkit	⬜️ Ignored (Inspect)	Visit Preview		May 23, 2024 3:47am
sui-kiosk	⬜️ Ignored (Inspect)	Visit Preview		May 23, 2024 3:47am
sui-typescript-docs	⬜️ Ignored (Inspect)	Visit Preview		May 23, 2024 3:47am

[tnowacki]

With the cut tomorrow, was surprised you needed to do this, but makes a bit of sense I suppose looking at what was enabled in 46

[tzakian]

Yea, was likewise surprised that there wasn't a protocol version sitting already for the cut. But yea, we definitely need to protocol config this change since it will change transaction effects.

[tzakian]

Of course there is now a merge conflict on another PR that landed that added 47... 🎉