[TA-3925]: API Versioning feature

[GuillemGarciaDev]

[TA-3925]: API Versioning feature

Description

This PR aims to add support for v1 and v2 rippled api versions. v2 is set as default for xrpl queries.

Type of change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Refactoring

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 where needed
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective
• New and existing unit tests pass locally with my changes

Changes

• add v1 sub package for xrpl/queries packages.

[notion-workspace]

API Versioning feature

[florent-uzio]

LGTM, but isn't there a way to include the V1 response directly into the V2 files instead of duplicating the files?

[GuillemGarciaDev]

LGTM, but isn't there a way to include the V1 response directly into the V2 files instead of duplicating the files?

We have chosen to group the queries by their versions, even if it means repeating code, and to set the latest version (in this case v2) as the default. This way, in future versions, we can ensure there is no confusion with requests or responses, as there will be a package for each version.