Upgrade jackson-jq to 1.0.0

[jamesnetherton]

Assuming this change is acceptable - any chance of having a new quarkus-jackson-jq release afterwards?

[hbelmiro]

Yes. We can release a new version once this is merged.

[ricardozanini]

@jamesnetherton @oscerd here: https://github.com/quarkiverse/quarkus-jackson-jq/releases/tag/2.1.0

[ricardozanini]

@jamesnetherton @oscerd unfortunately we can't release a new version because of this: https://github.com/quarkiverse/quarkiverse-release/actions/runs/11129100506/job/30925391635

The runtime-extra module is not a jar module and was added in the past so users could have the extra functions available in the scope.

The problem is that the fix won't fix the issue since the deployment module, as it is today, depends on it. Hence, it's adding the extras anyway!!

I don't have time to see this now, so we are blocked until I can fix it. The fix is simple. We must remove the extra module from the deployment module, update the docs to notify users about this change, and offer a new alternative to include the extras. The alternative must be a new module that users can add to their projects. Adding the extras from jq directly should do; in that case, we can create a BOM file to distribute.

[ricardozanini]

@jamesnetherton @oscerd fixed here #214