Embded move: part 1/x: Use local copy (#10418)

## Description 
This switches to using a local copy of Move (sui-move branch).

**NOTE: if you try to load the first commit `copy move/language @
dd68cce ...` your browser might freeze
because it's hundreds of thousands of lines.**
Only pay attention to the subsequent commits.
All features work.


Next steps:
* Enabling sync with upstream.
* Enabling clippy, fmt on Move workspace

## Test Plan 

Normal tests
---
If your changes are not user-facing and not a breaking change, you can
skip the following section. Otherwise, please indicate what changed, and
then add to the Release Notes section as highlighted during the release
process.

### Type of Change (Check all that apply)

- [ ] user-visible impact
- [ ] breaking change for a client SDKs
- [ ] breaking change for FNs (FN binary must upgrade)
- [ ] breaking change for validators or node operators (must upgrade
binaries)
- [ ] breaking change for on-chain data layout
- [ ] necessitate either a data wipe or data migration

### Release notes

Author: oxade

Cargo.lock

@@ -0,0 +1,112 @@
+[workspace]
+resolver = "2"
+
+members = [
+    "benchmarks",
+    "documentation/examples/diem-framework/crates/cli",
+    "documentation/examples/diem-framework/crates/crypto",
+    "documentation/examples/diem-framework/crates/crypto-derive",
+    "documentation/examples/diem-framework/crates/natives",
+    "evm/exec-utils",
+    "evm/extract-ethereum-abi",
+    "evm/move-ethereum-abi",
+    "evm/move-to-yul",
+    "extensions/async/move-async-vm",
+    "extensions/move-table-extension",
+    "move-analyzer",
+    "move-binary-format",
+    "move-binary-format/serializer-tests",
+    "move-borrow-graph",
+    "move-bytecode-verifier",
+    "move-bytecode-verifier/bytecode-verifier-tests",
+    "move-bytecode-verifier/fuzz",
+    "move-bytecode-verifier/invalid-mutations",
+    "move-bytecode-verifier/transactional-tests",
+    "move-command-line-common",
+    "move-compiler",
+    "move-compiler/transactional-tests",
+    "move-core/types",
+    "move-ir/types",
+    "move-ir-compiler",
+    "move-ir-compiler/move-bytecode-source-map",
+    "move-ir-compiler/move-ir-to-bytecode",
+    "move-ir-compiler/move-ir-to-bytecode/syntax",
+    "move-ir-compiler/transactional-tests",
+    "move-model",
+    "move-prover",
+    "move-prover/boogie-backend",
+    "move-prover/bytecode",
+    "move-prover/interpreter",
+    "move-prover/interpreter/crypto",
+    "move-prover/interpreter-testsuite",
+    "move-prover/lab",
+    "move-prover/move-abigen",
+    "move-prover/move-docgen",
+    "move-prover/move-errmapgen",
+    "move-prover/mutation",
+    "move-prover/test-utils",
+    "move-prover/tools/spec-flatten",
+    "move-stdlib",
+    "move-symbol-pool",
+    "move-vm/integration-tests",
+    "move-vm/paranoid-tests",
+    "move-vm/runtime",
+    "move-vm/test-utils",
+    "move-vm/transactional-tests",
+    "move-vm/types",
+    "testing-infra/module-generation",
+    "testing-infra/test-generation",
+    "testing-infra/transactional-test-runner",
+    "tools/move-bytecode-utils",
+    "tools/move-bytecode-viewer",
+    "tools/move-cli",
+    "tools/move-coverage",
+    "tools/move-disassembler",
+    "tools/move-explain",
+    "tools/move-package",
+    "tools/move-resource-viewer",
+    "tools/move-unit-test",
+    "tools/read-write-set",
+    "tools/read-write-set/dynamic",
+    "tools/read-write-set/types",
+]
+
+# NOTE: default-members is the complete list of binaries that form the "production Move codebase". These members should
+# never include crates that require fuzzing features or test features. These are the crates we want built with no extra
+# test-only code included.
+#
+# For more, see the "Conditional compilation for tests" section in documentation/coding_guidelines.md.
+default-members = [
+    "evm/extract-ethereum-abi",
+    "evm/move-to-yul",
+    "move-analyzer",
+    "move-ir-compiler",
+    "move-prover",
+    "move-prover/lab",
+    "move-prover/mutation",
+    "move-prover/tools/spec-flatten",
+    "move-compiler",
+    "move-stdlib",
+    "tools/move-disassembler",
+    "tools/move-bytecode-viewer",
+    "tools/move-cli",
+    "tools/move-coverage",
+    "tools/move-unit-test",
+]
+
+# Dependencies that should be kept in sync through the whole workspace
+[workspace.dependencies]
+bcs = "0.1.4"
+
+[profile.bench]
+debug = true
+
+[profile.dev]
+debug = true
+
+# use release settings to reduce memory pressure in the linking step in CI
+[profile.ci]
+inherits = "test"
+debug = 0 # for saving disk space during linking
+incremental = false
+codegen-units = 16

Cargo.toml

@@ -0,0 +1,24 @@
+---
+id: move-language
+title: Move Language
+custom_edit_url: https://github.com/move-language/move/edit/main/language/README.md
+---
+
+
+Move is a new programming language developed to provide a safe and programmable foundation for the Diem Blockchain.
+
+## Overview
+
+The Move language directory consists of four main parts:
+
+- [virtual machine](move-vm/) (VM) — contains the bytecode format, a bytecode interpreter, and infrastructure for executing a block of transactions. This directory also contains the infrastructure to generate the genesis block.
+
+- [bytecode verifier](move-bytecode-verifier/) — contains a static analysis tool for rejecting invalid Move bytecode. The virtual machine runs the bytecode verifier on any new Move code it encounters before executing it. The compiler runs the bytecode verifier on its output and surfaces the errors to the programmer.
+
+- [move-compiler](move-compiler/) — contains the Move source language compiler.
+
+- [standard library](move-stdlib/) — contains the standard library transaction scripts.
+
+## Exploring the Move language
+
+- You can find many small Move examples in the [tests](move-compiler/tests/move_check/) directory. The easiest way to experiment with Move is to create a new test in this directory and run it with `cargo test`.