fix(go): preserve uint64 ids during json unmarshal

[Obiajulu-gif]

This pull request introduces several improvements and fixes to the address and routing logic in the core Go package, with a focus on better handling of muxed accounts, improved error handling, and enhanced support for large routing IDs. The most significant changes include refactoring muxed account encoding/decoding, updating the detection of address kinds, improving the robustness of routing ID parsing and JSON unmarshalling, and adding comprehensive tests for edge cases.

Muxed Account Handling:

• Refactored muxed.DecodeMuxed and muxed.EncodeMuxed to use the updated strkey.MuxedAccount API for safer and more accurate muxed account processing, including stricter validation of muxed account IDs. [1] [2]

Address Detection and Parsing:

• Updated the Detect function to use more precise checks for muxed accounts and contracts, aligning with the latest strkey methods.
• Introduced the ParseResult and AddressError types to standardize address parsing results and error reporting.

Routing Logic and Error Handling:

• Improved ExtractRouting to handle errors from muxed account decoding gracefully, return appropriate error codes, and consistently process optional memo values. Routing IDs are now always wrapped in the RoutingID type. [1] [2] [3] [4]
• Added a helper function stringValue to safely dereference optional string pointers.

Routing ID Robustness:

• Implemented a custom UnmarshalJSON method for RoutingID to correctly handle both quoted and unquoted uint64 values, reject invalid or out-of-range numbers, and preserve the full uint64 range.
• Added thorough tests for RoutingID JSON unmarshalling, covering valid, edge, and invalid cases.

Dependency and Tooling Updates:

• Upgraded Go version to 1.22, updated the github.com/stellar/go dependency, and added indirect dependencies for improved build compatibility.
• Fixed a bug in the initialization of uint64Max in memo.go for correct big integer comparison.

These changes collectively improve the reliability and maintainability of address and routing handling, especially for muxed accounts and large routing IDs.

Closes #82

[drips-wave]

@Obiajulu-gif Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[codeZe-us]

@Obiajulu-gif PR reviewed, this is okay

[codeZe-us]

@Obiajulu-gif fix conflict in your branch

[codeZe-us]

@Obiajulu-gif please resolve conflicts

[Obiajulu-gif]

@codeZe-us i have fix the conflict