update SUI CLI to sui 1.63.3

[FelixFan1992]

No description provided.

[github-actions]

👋 FelixFan1992, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[FelixFan1992]

currently, we can use a hack:

[published.testnet]
chain-id = "4c78adac"
published-at = "0x0000000000000000000000000000000000000000000000000000000000000000"
original-id = "0x0000000000000000000000000000000000000000000000000000000000000000"
version = 1

but this is not ideal. waiting for Sui team to release a new approach

[faisal-chainlink]

Seems like the primary remaining item in this PR is the insufficient gas error. Likely due to account selection in the CLI.

[faisal-chainlink]

@FelixFan1992 Currently all tests should pass with the exception of the upgrades via MCMS. The issue with MCMS upgrades is that we are still using the CLI the build the compiled package.

Note: I'm running the relaying and binding tests with go test ./... -v -tags=integration -count=1 -p=1 from the main directory. For the /integration-tests directory, it's the same command but needs to be run within the subdirectory since it's a separate module. This is slightly different from how CI is running them but we can handle that afterwards.

When using the --with-unpublished-dependencies, I'm seeing an "incompatible upgrade" error. However, if we use the regular publishing flow to generate the byte code of a package, we must also fill in all the addresses of the dependencies which isn't currently done.

That should be the last missing piece.

---

The summary is that we are now creating the Published.toml file or pub.[env].toml file whenever we want to handle a given contract deployment. We start by traversing all the deps for that contract and build their toml files one by one to enable publishing / compiling.