rosetta delegator address balances

[defnotzed]

Description

Implement the delegator address balances rosetta endpoint.

The rosetta client should manage its own delegator and pool address relationship when fetching relevant data.
The request payload should look like this (added the metadata field under sub_account_identifier):

"account_identifier": {
    "address": "0x899d44dca988af7895cdc9828ae0e7f6c5c42d74fa1610e693fb5f613cb8c09a", // owner/delegator address
    "sub_account": {
        "address": "active_stake", // string active
        # this is the new field added
        "metadata": {
            "pool_address": "0xbd50bb20e1972747db365c3a6e31255d78867c6b8df9877ea6054bb335dd6031" // pool_address
        }
    }
}

About balance fetching:
Using delegator address 0x65b1e4d62e803d7e3a5c715baa33391757ae530c9fef287bf2d7d15c1ea6e3e6 and its validator address 0x2ded75e99c6efbe143a9648a3e88ebf9d0cf249b2af44d510bdd0287e8adcc79 as an example

The response should be similar to native staking:
Variables that should be fetched from the delegator address:

1. Sequence number from its 0x1::account::Account resource
2. Balances from delegation_pool.move get_stake() function

Variables should be fetched from the pool address:
1. Operator from 0x1::stake::StakePool resource
2. Lockup until secs from 0x1::stake::StakePool resource

Test Plan

Tested with remote online node from e2e
delegated staking balance

native staking balance

direct balance

[xindingw]

nit: Maybe throw "Unable to construct BalanceResult instance" error here?

[xindingw]

LGTM! Let me know if you need me to find another approver.

[github-actions]

✅ Forge suite compat success on testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> 515f1381d6af5c8a44bddfa004ff15931db513d9

Compatibility test results for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> 515f1381d6af5c8a44bddfa004ff15931db513d9 (PR)
1. Check liveness of validators at old version: testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b
compatibility::simple-validator-upgrade::liveness-check : 10100 TPS, 3700 ms latency, 6400 ms p99 latency,no expired txns
2. Upgrading first Validator to new version: 515f1381d6af5c8a44bddfa004ff15931db513d9
compatibility::simple-validator-upgrade::single-validator-upgrade : 6044 TPS, 6843 ms latency, 11000 ms p99 latency,no expired txns
3. Upgrading rest of first batch to new version: 515f1381d6af5c8a44bddfa004ff15931db513d9
compatibility::simple-validator-upgrade::half-validator-upgrade : 5630 TPS, 7003 ms latency, 9200 ms p99 latency,no expired txns
4. upgrading second batch to new version: 515f1381d6af5c8a44bddfa004ff15931db513d9
compatibility::simple-validator-upgrade::rest-validator-upgrade : 8085 TPS, 4696 ms latency, 8900 ms p99 latency,no expired txns
5. check swarm health
Compatibility test for testnet_2d8b1b57553d869190f61df1aaf7f31a8fc19a7b ==> 515f1381d6af5c8a44bddfa004ff15931db513d9 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite land_blocking success on 515f1381d6af5c8a44bddfa004ff15931db513d9

performance benchmark : 5827 TPS, 6800 ms latency, 26400 ms p99 latency,(!) expired 383 out of 2488640 txns
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite framework_upgrade success on aptos-node-v1.3.0_3fc3d42b6cfe27460004f9a0326451bcda840a60 ==> 515f1381d6af5c8a44bddfa004ff15931db513d9

Compatibility test results for aptos-node-v1.3.0_3fc3d42b6cfe27460004f9a0326451bcda840a60 ==> 515f1381d6af5c8a44bddfa004ff15931db513d9 (PR)
Upgrade the nodes to version: 515f1381d6af5c8a44bddfa004ff15931db513d9
framework_upgrade::framework-upgrade::full-framework-upgrade : 6042 TPS, 6487 ms latency, 11100 ms p99 latency,no expired txns
5. check swarm health
Compatibility test for aptos-node-v1.3.0_3fc3d42b6cfe27460004f9a0326451bcda840a60 ==> 515f1381d6af5c8a44bddfa004ff15931db513d9 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Test runner output
• Test run is land-blocking