Add geopatch to node transactions

[wassimans]

Description

This pull request introduces the systematic addition of a geopatch to node transactions. This change ensures that the geopatch is included in node transactions and validated during the transaction lifecycle.

The update impacts the election of storage and validation nodes, as it now relies on the validated geopatch from node transactions rather than local calculations. This approach resolves inconsistencies caused by potential updates to the MMDB2 database.

This change introduces:
• The inclusion of the geopatch in node transactions.
• Migration script to add the geopatch to existing nodes transactions.
• Updated tests to validate the geopatch functionality.
• Enhanced core modules for encoding, decoding, and validating geopatches.

Fixes #1576 #1613

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Functional Tests

• Functionally validated the migration script by running it on a network of test nodes.
• Verified the inclusion of the geopatch in updated transactions and ensured proper validation in subsequent operations.
• Transaction Content Validation: Validated that node transactions include geopatch information and that it is correctly decoded during transaction processing.
• Invalid Geopatch Handling: Ensured that transactions with invalid geopatches are rejected.

Unit Tests

• Enhanced existing test cases for Node.encode_transaction_content/1 and Node.decode_transaction_content/1 to include geopatch validation.
• Added new tests in GeoPatchTest for geopatch calculation and decoding.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules