feat: implement new RPCs getrawislock and getrawbestchainlock

[knst]

it's a draft because I need a confirmation from pshenmic that it works as he expects.

Issue being fixed or feature implemented

#6391

To register an identity in the DashPlatform network, there is a required field of InstantLock or ChainLock buffer in IdentityCreateTransition. You first create and broadcast Core transaction, then wait for InstantLock or ChainLock, and then create and broadcast transaction in the Platform chain with that data.

What was done?

Implemented 2 new RPC getrawislock and getrawbestchainlock which output is similar to ZMQ output.

How Has This Been Tested?

See new asserts in functional test interface_zmq_dash.py

Breaking Changes

N/A

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation
• I have assigned this pull request to a milestone

[DashCoreAutoGuix]

Guix Automation has began to build this PR tagged as v22.1.0-devpr6455.a4256c92. A new comment will be made when the image is pushed.

[DashCoreAutoGuix]

Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v22.1.0-devpr6455.a4256c92. The image should be on dockerhub soon.

[kwvg]

Consider defining llmq_ctx outside the loop

[knst]

I will wait feedback from pshenmic first

[kwvg]

Consider

if (auto islock = CHECK_NONFATAL(llmq_ctx.isman)->GetInstantSendLockByTxid(txid); islock != nullptr) {
    CDataStream ssTx(SER_NETWORK, PROTOCOL_VERSION);
    ssTx << *islock;
    result_arr.push_back(HexStr(ssTx));
} else {
    result_arr.push_back("None");
}