[Bug] `cargo run -p movement -- node run-local-testnet` crashes

[andygolay]

🐛 Bug

On the movement branch, cargo run -p movement -- node run-local-testnet crashes with

One of the services failed to start up, running shutdown steps...
Ran shutdown steps
Unexpected error: 
One of the services crashed on startup:
Ok(
    Err(
        Error {
            context: "Service ended with an error",
            source: Error {
                context: "Failed to build Funder",
                source: Error {
                    context: "Failed to build MintFunder",
                    source: Error {
                        context: "Failed to make MintFunder use delegated account",
                        source: Error {
                            context: "Failed to delegate minting to the new account",
                            source: Unknown(
                                "Transaction committed on chain, but failed execution: Move abort in 0x1::system_addresses: ENOT_APTOS_FRAMEWORK_ADDRESS(0x50003): The address/account did not correspond to the core framework address",
                            ),
                        },
                    },
                },
            },
        },
    ),
)

on the movement branch.

Also, in aptos-labs/aptos-core / main branch, cargo run -p movement -- node run-local-testnet is failing locally for me, with

$ aptos node run-local-testnet
Unexpected error: Failed to build node service manager: Failed to load / create config for node: Unable to load config: Yaml("config", Message("unknown field `max_concurrent_network_reqs`, expected one of `max_connection_delay_ms`, `connection_backoff_base`, `connectivity_check_interval_ms`, `network_channel_size`, `discovery_method`, `discovery_methods`, `identity`, `listen_address`, `mutual_authentication`, `network_id`, `runtime_threads`, `inbound_rx_buffer_size_bytes`, `inbound_tx_buffer_size_bytes`, `outbound_rx_buffer_size_bytes`, `outbound_tx_buffer_size_bytes`, `seed_addrs`, `seeds`, `max_frame_size`, `enable_proxy_protocol`, `ping_interval_ms`, `ping_timeout_ms`, `ping_failures_tolerated`, `max_outbound_connections`, `max_inbound_connections`, `inbound_rate_limit_config`, `outbound_rate_limit_config`, `max_message_size`, `max_parallel_deserialization_tasks`, `enable_latency_aware_dialing`", Some(Pos { marker: Marker { index: 1095, line: 35, col: 4 }, path: "full_node_networks[0]" })))

To reproduce

Run the above commands from the root, on the appropriate branch (movement or main).

Stack trace/error message

// Paste the output here

Expected Behavior

The localnet should run successfully and not crash.