fix: estimateMessageFee should handle from_address as checksum'ed eth address

[SergeyVolynkin]

Motivation and Resolution

While using estimateMessageFee in our deposit/withdraw code, we encountered that passing from_address: 0x01FB18b564c106873ea2951F0f099Af7527E8680 argument to estimateMessageFee causes the following error:

Caused by: LibraryError: RPC: starknet_estimateMessageFee with params {"message":{"from_address":"0x1fb18b564c106873ea2951f0f099af7527e8680","to_address":"0x1e58499da87cf11a2bc75b035f13c5ca3dd7be2ccf6e381714c879b3caa64f6","entry_point_selector":"0x2d757788a8d8d6f21d1cd40bce38a8222d70654214e96ff95d8086e684fbee5","payload":["0x3ab1ead7a1fe8b63ca757ae094268b1f1287a95b36f262bc9ed4ee1900849f7","0x2faf080","0x0"]},"block_id":"pending"}
 -32602: Invalid params: {"reason":"invalid length 39, expected a (both 0x-prefixed or not) hex string or byte array containing 20 bytes at line 1 column 70"}

From the source code, starknet.js seem to convert the hex string to bigint and then back to hex which loses the leading 0x0… our from_address address, which causes incorrect from_address address to be sent

RPC version (if applicable)

v0_6, v0_7

Usage related changes

No breaking changes

Development related changes

No breaking changes

Checklist:

• Performed a self-review of the code
• Rebased to the last commit of the target branch (or merged it into my branch)
• Linked the issues which this PR resolves
• Documented the changes in code (API docs will be generated automatically)
• Updated the tests
• All tests are passing

[penovicp]

This was reported in #1028 and addressed with the #1040 PR. The PR was merged to the next-version branch which should be merged to develop soon.

In any case, thank you for being proactive about the issue.

[SergeyVolynkin]

Closing in favor of #1040, thank you @penovicp