Integrate ZSA-related state enhancements and new getassetstate RPC call

[dmidem]

This update incorporates the latest state enhancements for ZSA, including tracking the asset total supply and finalization flag. Additionally, the getassetstate RPC call has been implemented to allow querying the state of specific assets. See PRs #26, #32, and #29 for more details.

getassetstate call be tested using the following curl command after starting the node:

curl -X POST http://127.0.0.1:18232/ \
     -H "Content-Type: application/json" \
     -d '{
           "jsonrpc": "1.0",
           "id": "curltest",
           "method": "getassetstate",
           "params": ["c9cd432edea87319b8bdf5b400d17cb0d4743f2174c15037c7fd9e5cdce94586"]
         }'

Ensure to replace the params with the correct hex-encoded asset ID (asset base) and specify the correct port and address.

You can also specify an optional boolean flag in params to include assets from the non-finalized state in the response. The flag defaults to true if omitted. For example:

...
"params": ["c9cd432edea87319b8bdf5b400d17cb0d4743f2174c15037c7fd9e5cdce94586", false]
...

[PaulLaux]

It's better to ignore single lines (and fix later) than disable entirely
https://stackoverflow.com/a/55402970

[arya2]

Actually, this could make it harder to consistently serialize in the same order, I'll add the check here.

[dmidem]

@arya2 I have a couple of questions about the asset state management code.

1. When I make a getassetstate RPC call using curl, I receive the error message "IO error: failed to fill whole buffer". This occurs when the asset base parameter in the query is invalid (e.g., an empty string). Could we return a more relevant error message in this case?

2. Do you have any validation checks in the code to ensure that an asset has is_finalized = false in the existing state before making any new state changes to it? (@PaulLaux, or this needs to be checked in the consensus part?)

[arya2]

1. When I make a getassetstate RPC call using curl, I receive the error message "IO error: failed to fill whole buffer". This occurs when the asset base parameter in the query is invalid (e.g., an empty string). Could we return a more relevant error message in this case?

Yep, thank you for catching that.

2. Do you have any validation checks in the code to ensure that an asset has is_finalized = false before making any state changes to it? (@PaulLaux, or this needs to be checked in the consensus part?)

apply_finalization() checks that either an asset state isn't finalized or the change doesn't include any issuance, so it currently allows burning finalized assets.