Support executing an OASFilter during multiple run stages

[Postremus]

This provides multiple differentiated RunStages during which an OASFilter can be run.

Fixes #52481

[Postremus]

/cc @MikeEdgar @HerrDerb

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit bede64c.

✅ 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.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[github-actions]

🙈 The PR is closed and the preview is expired.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit bede64c.

✅ 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.

You can consult the Develocity build scans.

[MikeEdgar]

Thanks for working on this @Postremus . I didn't spot any issues with the changes.

[HerrDerb]

@Postremus Thank you very much 👍

[gsmet]

If @MikeEdgar is happy, let’s merge it.

Does it break compatibility or we can backport to 3.32?

[Postremus]

The changes are designed to be backwards compatible with the behaviour of 3.31. So i would say can be backported to 3.32.

[Postremus]

But tbh does not need to be back ported to 3.32.
The users problem with 3.31 was solved by setting the always-run config property.

So +0 on backport.

We might want to add a few lines for the 3.31 migration guide, explaining the eager Vs first request execution change. Will prepare something later.

[gsmet]

I think it’s worth having it in the next LTS so will backport.

[Postremus]

@gsmet
For the 3.31 migration guide:

Smallrye OpenAPI:


If you require your OpenApiFilter to run at request time instead of startup time, make sure to configure `quarkus.smallrye-openapi.always-run-filter=true`.

Runtime filters were executed on first request, not on startup, meaning that for example the vert.x request context of that first request would be available. On second request, such runtime filters would not be executed again, leading to the OpenAPI document containing stale changes based on the first request.

OASFilter annotated as `@OpenApiFilter` (or `@OpenApiFilter(OpenApiFilter.RunStage.RUN)`) now correctly execute eagerly on startup, like the documentation already suggested they were:

```
Runtime filters by default runs on startup (when the final OpenAPI document gets created).
```
(https://quarkus.io/version/3.27/guides/openapi-swaggerui#runtime-filters)