[Bug][move-compiler-v2] Review pre-defined addresses in `move-compiler/tests/move_check_testsuite.rs` for V2 tests

[brmataptos]

🐛 Bug

v1's move_check_testsuite.rs defines a set of named addresses for all tests. To port V1 tests we will need some of these, but perhaps adding them all could result in conflicts with other named addresses in V2 tests.

fn default_testing_addresses() -> BTreeMap<String, NumericalAddress> {
    let mapping = [
        ("aptos_std", "0x1"),
        ("std", "0x1"),
        ("M", "0x1"),
        ("A", "0x42"),
        ("B", "0x42"),
        ("K", "0x19"),
        ("Async", "0x20"),
    ];

It appears that -std is used in various tests

• aptos_std we need for tests of certain warning suppressions in aptos libs.
• move-compiler/tests/move_check/parser/named_address.move depends on M being defined.
• move-compiler/tests/move_check/naming/named_address_distinct_from_each_others_value.move depends on A and B being defined to the same value.
• move-compiler/tests/move_check/flavors/async/ has several tests using Async
• move-compiler/tests/move_check/expansion/duplicate_module_after_mapping.move uses A, B, and K.

But

• From comments in the file, move-compiler/tests/move_check/to_bytecode/unassigned_address.move depends on A not being defined (but it is, so the test does not fail as it should).

I think that we should:

• Fix move-compiler/tests/move_check/to_bytecode/unassigned_address.move to use a symbol not defined in the list above.
• Add these symbols to V2 tests to facilitate V1 test porting, but also be aware of them.

[brmataptos]

@rahxephon89 @vineethk please review.

[vineethk]

@brmataptos Given that M, A, B, K all have specific test folders associated with them, what do you think about the alternative: for these named addresses, we only add them through test configs for those specific folders.

It is really easy to forget that these are supposed to be standard "test" addresses.

Another option is to use different unique names (aptos_testing_M, etc) that are harder to inadvertently use in our tests, and then change the existing tests to use these names instead.

[brmataptos]

Note that named addresses in tests are pretty uncommon.