Refactor upstream guardrails

[edeandrea]

Refactor to use upstream guardrails (instead of #1619).

For now I'm leaving the existing Quarkus-specific implementation in place, but fully deprecated. We can decide if we'd like to rip it out as part of this PR, or have both implementations for a little bit of time in order to give people time to transition.

• Closes Refactor guardrails once they are moved upstream #1284

[geoand]

cc @mariofusco

[quarkus-bot]

Status for workflow Build (on pull request)

This is the status report for running Build (on pull request) on commit cbb10d7.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

[mariofusco]

@edeandrea thanks a lot, amazing job!

I strongly suggest to remove the old guardrails implementation immediately, or anyway before putting out a new release. For users the migration from one implementation to another will be quite trivial and having both versions around will only confuse them.

I don't mind if you want to remove the legacy part within this PR or in a subsequent one, that's up to you and both alternatives are ok for me. I just have a small preference in removing the old stuff in this PR because in this way we will have the integration tests running also against those removals and be sure that none of the old parts is still in use.

Also don't forget to update documentation accordingly.

[edeandrea]

Also don't forget to update documentation accordingly.

Already part of this PR!

I strongly suggest to remove the old guardrails implementation immediately, or anyway before putting out a new release

I believe there is a conversation in the issue for this PR about that. This PR deprecated all the Quarkus-specific implementations. I'll soon work on one (couple of weeks) that will remove it.

[mariofusco]

I strongly suggest to remove the old guardrails implementation immediately, or anyway before putting out a new release

I believe there is a conversation in the issue for this PR about that. This PR deprecated all the Quarkus-specific implementations. I'll soon work on one (couple of weeks) that will remove it.

If so it's ok for me to merge this PR. /cc @geoand

[edeandrea]

@mariofusco / @geoand See #1735 for work for removing the Quarkus-specific implementation. I'm at an event this week so I will start working on it next week.