Prettify Aptos CLI -> Movement CLI (#224)

## Description
<!-- Please include a summary of the change, including which issue it
fixes or what feature it adds. Include relevant motivation, context and
documentation as appropriate. List dependencies that are required for
this change, if any. -->

Address #216

- Rename the misnomers: **Done**
- Fix cosmetics : **Done**
- Update any static URLs: **Done**
- Check the precompiled binary : **Not Done**. See binaries remark.

- Easy build of Movement CLI (homebrow or [current
script](https://docs.movementnetwork.xyz/devs/movementcli#quick-install-movement-precompiled-binaries)
built by Andy G): **Not done**. The entire process should be rethought
to generate the binaries build using GitHub CI and a more robust
Homebrew integration, rather than simply downloading the binary.
- When we init Move.toml should use our fork of the framework instead of
builders having to populate: Done
- Mainnet, Testnet, Devnet should populate movement endpoints for rpc:
**Done**
- Successful transactions with link to our explorer: **Done**
- New account creation should hit our faucet for initial account
initialization: **Done**

## Type of Change
- [ ] New feature
- [ ] Bug fix
- [ ] Breaking change
- [ ] Performance improvement
- [X] Refactoring
- [ ] Dependency update
- [ ] Documentation update
- [ ] Tests

## Which Components or Systems Does This Change Impact?
- [ ] Validator Node
- [ ] Full Node (API, Indexer, etc.)
- [ ] Move/Aptos Virtual Machine
- [ ] Aptos Framework
- [X] Aptos CLI/SDK
- [] Developer Infrastructure
- [ ] Other (specify)

## How Has This Been Tested?
<!--
- Please ensure that the functionality introduced by this change is well
tested and verified to work as expected.
- Ensure tests cover both happy and unhappy paths.
- List and link relevant tests.
-->
I built all targets and ran the tests.
I've created a new account, invited a new smart contract, and deployed
it.


## Key Areas to Review
<!--
- Identify any critical parts of the code that require special attention
or understanding. Explain why these parts are crucial to the
functionality or architecture of the project.
- Point out any areas where complex logic has been implemented. Provide
a brief explanation of the logic and your approach to make it easier for
reviewers to follow.
- Highlight any areas where you are particularly concerned or unsure
about the code's impact on the change. This can include potential
performance or security issues, or compatibility with existing features.
-->

## Checklist
- [ ] I have read and followed the
[CONTRIBUTING](https://github.com/aptos-labs/aptos-core/blob/main/CONTRIBUTING.md)
doc
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I identified and added all stakeholders and component owners
affected by this change as reviewers
- [ ] I tested both happy and unhappy path of the functionality
- [ ] I have made corresponding changes to the documentation

<!-- Thank you for your contribution! -->

Author: andygolay

Cargo.lock

@@ -292,7 +292,7 @@ rust-version = "1.80.1"
 [workspace.dependencies]
 # Internal crate dependencies.
 # Please do not add any test features here: they should be declared by the individual crate.
-aptos = { path = "crates/aptos" }
+movement = { path = "crates/aptos" }
 aptos-accumulator = { path = "storage/accumulator" }
 aptos-admin-service = { path = "crates/aptos-admin-service" }
 aptos-aggregator = { path = "aptos-move/aptos-aggregator" }

Cargo.toml

@@ -14,7 +14,7 @@ rust-version = { workspace = true }
 
 [dependencies]
 anyhow = { workspace = true }
-aptos = { workspace = true, features = [ "no-upload-proposal" ] }
+movement = { workspace = true, features = [ "no-upload-proposal" ] }
 aptos-build-info = { workspace = true }
 aptos-crypto = { workspace = true }
 aptos-framework = { workspace = true }

aptos-move/aptos-release-builder/Cargo.toml

@@ -30,7 +30,7 @@ pub fn generate_upgrade_proposals(
         "only multi-step proposals can have a next execution hash"
     );
 
-    const APTOS_GIT_PATH: &str = "https://github.com/aptos-labs/aptos-core.git";
+    const MVT_APTOS_GIT_PATH: &str = "https://github.com/movementlabsxyz/aptos-core.git";
 
     // NOTE: This is skipping 0x7 (aptos-experimental package) which is only meant to be released
     // to devnet (or local testnet) via the genesis process and never released/upgraded in testnet

aptos-move/aptos-release-builder/src/components/framework.rs

@@ -10,7 +10,6 @@ use crate::{
     },
 };
 use anyhow::{anyhow, bail, Context, Result};
-use aptos::governance::GenerateExecutionHash;
 use aptos_crypto::HashValue;
 use aptos_gas_schedule::LATEST_GAS_FEATURE_VERSION;
 use aptos_infallible::duration_since_epoch;
@@ -27,6 +26,7 @@ use aptos_types::{
 use futures::executor::block_on;
 use handlebars::Handlebars;
 use move_binary_format::file_format_common::VERSION_DEFAULT_LANG_V2;
+use movement::governance::GenerateExecutionHash;
 use once_cell::sync::Lazy;
 use serde::{de::Visitor, Deserialize, Deserializer, Serialize, Serializer};
 use std::{

aptos-move/aptos-release-builder/src/components/mod.rs

@@ -56,9 +56,9 @@ impl NetworkSelection {
         use NetworkSelection::*;
 
         let s = match &self {
-            Mainnet => "https://fullnode.mainnet.aptoslabs.com",
-            Testnet => "https://fullnode.testnet.aptoslabs.com",
-            Devnet => "https://fullnode.devnet.aptoslabs.com",
+            Mainnet => "https://mainnet.movementnetwork.xyz",
+            Testnet => "https://testnet.movementnetwork.xyz",
+            Devnet => "https://devnet.movementnetwork.xyz",
             RestEndpoint(url) => url,
         };
 
@@ -159,7 +159,7 @@ pub enum Commands {
     },
     /// Print out current values of on chain configs.
     PrintConfigs {
-        /// Url endpoint for the desired network. e.g: https://fullnode.mainnet.aptoslabs.com/v1.
+        /// Url endpoint for the desired network. e.g: https://mainnet.movementnetwork.xyz/v1.
         #[clap(short, long)]
         endpoint: url::Url,
         /// Whether to print out the full gas schedule.
@@ -175,7 +175,7 @@ pub enum Commands {
     /// Usage: --endpoint '<URL>'
     /// --package-address <ADDRESS> --package-name <PACKAGE_NAME> [--print-json]
     PrintPackageMetadata {
-        /// Url endpoint for the desired network. e.g: https://fullnode.mainnet.aptoslabs.com/v1.
+        /// Url endpoint for the desired network. e.g: https://mainnet.movementnetwork.xyz/v1.
         #[clap(short, long)]
         endpoint: url::Url,
         /// The address under which the package is published