Feature/ansible galaxy v3 compatibility

[angeloxx]

Implemented compatibility with ansible galaxy v3

This pull request makes the following changes:

• add support to v3 api for collection
• backward compatibility with older ansible engine, converting api from v2 to v3

It relates to the following issue:

• Fixes Unable to install collection from new Galaxy #23

cc @DarthHater @bhamail @l3ender

[lamm]

@l3ender : When do you think you can integrate this fix into a next release?

[cniweb]

@l3ender : When do you think you can integrate this fix into a next release?

[l3ender]

Thanks for this PR! My apologies for missing it the first time around.

I've noticed your recent activity, so please tag me when it's ready to go. Thanks again!

[angeloxx]

I updated the PR in order to support GitHub actions and release the new version simply tagging the code with version (eg. v0.3.3). Once released, we have to update again the code in order to built with Java 17 and support Nexus 3.69+ (https://help.sonatype.com/en/sonatype-nexus-repository-system-requirements.html) and check if works properly with PostgreSQL because embedded OrientDB (which I used to test the plugin, version 3.68.0) is no longer supported.

Nexus Repository no longer supports OrientDB, Java 8, or Java 11 in future releases. OrientDB users must migrate to H2 or PostgreSQL before upgrading to version 3.71.0

Once merged we can close this issue and check if further changes are needed. Readme was updated with reference to "this" version (0.3.3) and marked 0.4.x as TBD.

[l3ender]

Thanks again for this PR and the work in it!

I like the thought of using workflows/actions for a validate/release pipeline (less manual work), but is it possible to keep those changes in a separate PR?

Other than that, the changes look good and I'm good to proceed with merge/release of the update. Please note that I didn't run/test these locally.

Thanks again!