[move] Remove hardhat on Move

[georgemitenkov]

Description

We do not need hardhat on Move.

1. No one work or will work on this in the near future.
2. If ecosystem builds things, it is better that we keep move repo small and nice, and things like "move-on-evm" are built around. Otherwise we end up changing Move in order to make sure EVM things work (which is the case of V1 compiler, and its EVM and async flavours)
3. Even if we want to keep Move to yul, etc., hardhat is really not needed, + we have Aptos workspace.

How Has This Been Tested?

Key Areas to Review

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• 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
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING 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

[trunk-io]

⏱️ 17m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
rust-move-tests	13m	🟩
rust-cargo-deny	2m	🟩
check-dynamic-deps	40s	🟩
general-lints	31s	🟩
semgrep/ci	20s	🟩
file_change_determinator	14s	🟩
permission-check	4s	🟩
permission-check	2s	🟩
check-branch-prefix	1s	🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[georgemitenkov]

• [move] Remove hardhat on Move #15462 👈 (View in Graphite)
• [move] Use workspace dependencies for third-party/move #15461
• [move] Change copybara to sync with move-on-aptos #15458
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.