v3.0: fix: use proper serialization for versioned messages in get_fee_for_m… (backport of #7719)

[mergify]

Fix versioned message serialization in get_fee_for_message

Problem

get_fee_for_message was failing with "index out of bounds" errors when used with v0 messages containing Address Lookup Tables. The root cause was that bincode::serialize() doesn't include the MESSAGE_VERSION_PREFIX (0x80) required for v0 messages, causing the RPC endpoint to misinterpret the serialized message format.

Solution

Added a serialize_message() method to the SerializableMessage trait that uses the proper native serialization for each message type. For v0 messages, this includes the required version prefix, while legacy messages remain unchanged. Updated get_fee_for_message() to use this new serialization method instead of bincode::serialize().

The fix ensures that both legacy messages and v0 messages with Address Lookup Tables are properly serialized when calling get_fee_for_message(). Added comprehensive tests to verify the serialization behavior and ensure no regressions.

Closes #7563

Can you pls check this @KirillLykov @0xbrw

---

This is an automatic backport of pull request #7719 done by Mergify.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 92.85714% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.4%. Comparing base (e558db5) to head (ee07863).

Additional details and impacted files

@@            Coverage Diff            @@
##             v3.0    #8139     +/-   ##
=========================================
- Coverage    83.4%    83.4%   -0.1%     
=========================================
  Files         810      810             
  Lines      365464   365533     +69     
=========================================
+ Hits       305120   305165     +45     
- Misses      60344    60368     +24     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.