fix: lookup tables ordering

[sonicfromnewyoke]

Problem

neither #364 nor #344 completely fix the issue with non-deterministic v0 message with multiple address lookup tables

Summary of Changes

• sort map keys before iterating in NewTransaction
• fix serialization format
• use tests from the original solana-sdk to verify correctness of work

should suppress #344 #364

cc @daog1

[HealthyBuilder]

Hey @sonicfromnewyoke, CI on main is red after merging both #296 and #365.
The root cause: #296 added a PublicKey tiebreaker to AccountMeta.less(), which changes the deterministic ordering of Message.AccountKeys. The hardcoded expected values in transaction_test.go now need to be updated to match:

TestNewTransaction (lines 87-97)
TestTransactionSerializePumpFunSwap (line 364)

Can you submit a quick fix PR to update these expected values? Just run the tests locally, grab the new deterministic output, and update the assertions. Thanks!