Makes network=mainnet work properly in Rosetta

[bkase]

When Rosetta is built with the mainnet profile, report (correctly) that the network being used in mainnet.

[bkase]

@jspada is testing this against the new ledger build now!

[jspada]

Works for me!

mainnet

REQUEST = {"metadata": {}}

Getting network identifier... mainnet

RESPONSE = {"network_identifiers": [{"blockchain": "coda", "network": "mainnet"}]}

testnet

REQUEST = {"metadata": {}}

Getting network identifier... testnet

RESPONSE = {"network_identifiers": [{"blockchain": "coda", "network": "testnet"}]}

[mrmr1993]

Code looks good; I haven't tested, so I'll assume that you or @jspada will.

[jspada]

Slightly different behaviour. In Brandon's previous fix it used to report testnet when rosetta was built with --profile=testnet_postake_medium_curves and mainnet when rosetta was built with --profile=mainnet

In the new version of the fix it seems depend on what profile mina is built with (rather than rosetta) and reports debug or mainnet instead.

$ dune build src/app/cli/src/mina.exe --profile=mainnet
$ test-rosetta
REQUEST = {"metadata": {}}
RESPONSE = {"network_identifiers": [{"blockchain": "coda", "network": "mainnet"}]}

$ dune build src/app/cli/src/mina.exe --profile=testnet_postake_medium_curves
$ test-rosetta
REQUEST = {"metadata": {}}
RESPONSE = {"network_identifiers": [{"blockchain": "coda", "network": "debug"}]}

Is this the desired behaviour?