[Compiler-v2] Fix test plan in move-unit-test to use compiler v2

[rahxephon89]

Description

This PR closes #15385 by explicitly using test plan builder v2 in move-unit-test when MOVE_COMPILER_V2 is set to true.

How Has This Been Tested?

Existing test cases in move-unit-test, see updated baseline files.

Key Areas to Review

Whether flags are correctly set when running tests using Compiler v2.

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]

⏱️ 33m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
rust-move-tests	13m	🟩
rust-move-tests	12m	🟩
rust-cargo-deny	4m	🟩 🟩
check-dynamic-deps	1m	🟩 🟩
general-lints	53s	🟩 🟩
semgrep/ci	53s	🟩 🟩
file_change_determinator	20s	🟩 🟩
permission-check	8s	🟩 🟩
permission-check	6s	🟩 🟩

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