M1 Refactor, Movement SDK, Standalone Sui Execution, M2 as Movement SDK

[l-monninger]

Pull Request

Description

• This contribution represents a trivial change (skip the following sections).
• This contribution represents a CI/CD change that needs to be tested e2e (skip the following sections; justify below).
  This PR incudes commits for
• M1 Subnet Refactor (for code quality)
• Development of Movement SDK (for internal organization)
• Development of Standalone Sui Execution

Motivation and Context

Changes Made

• Comprehensive changes to organization of M1, initially as an individual refactor, later as an migration to the Movement SDK.
• Movement SDK framework crate added
• Standalone Sui Execution developed against Movement SDK

Testing

• Testing still in early stages
  • Initial subnet refactor appears to produce the same behavior

Screenshots (if applicable)

Related Issues

Checklist

• I have read and followed the project's contributing guidelines.
• I have tested the changes thoroughly.
• My code follows the style and formatting guidelines of the project.
• I have updated the relevant documentation, if applicable.
• I have added tests, if appropriate.
• The code builds without any errors or warnings.
• All existing tests pass successfully.

Additional Notes

[l-monninger]

Daily checkpoint for Oct 16, 2023. Mainly Movement SDK and Sui planning.

[l-monninger]

Note that lint check with this PR will fail as its development preceded the adoption of the Conventional Commits standard.

[l-monninger]

canonical-new has reintroduced a lot of the above, but in a very different way. I am going to close this for now and not merge. However, outstanding elements of the M1 Refactor should likely be reincorporated from this branch at a later date.