feat!: update dfx cycles commands with maninet cycles-ledger canister ID

[smallstepman]

Description

The canister ID for cycles-ledger became known, therefore, it is no longer required to pass it as an CLI argument.

How Has This Been Tested?

covered by CI

Checklist:

• The title of this PR complies with Conventional Commits.
• I have edited the CHANGELOG accordingly.
• I have made corresponding changes to the documentation.

[ericswanson-dfinity]

This will probably also require a change to assets/cycles-ledger/dfx.json and/or utils/cycles-ledger.bash in order to create the canister locally with the expected principal.

[smallstepman]

@ericswanson-dfinity would the following approach suffice:

  assert_command dfx deploy cycles-ledger --specified-id "um5iw-rqaaa-aaaaq-qaaba-cai"
  assert_command dfx deploy cycles-depositor --argument "(record {ledger_id = principal \"$(dfx canister id cycles-ledger)\"})" --with-cycles 10000000000000 --specified-id "ul4oc-4iaaa-aaaaq-qaabq-cai"

or should I deploy them separately from test's dfx.json, and reference them as remote canisters?

[ericswanson-dfinity]

@ericswanson-dfinity would the following approach suffice:

Yes, dfx deploy --specified-id is fine.