Refactor webhook discovery and scanning mechanism

[zdary]

Implement package-based filtering for webhooks
This commit introduces support for filtering webhooks based on the springdoc.packages-to-scan and springdoc.packages-to-exclude properties. This provides users with more granular control over which webhooks are included in the generated OpenAPI specification, aligning their behavior with that of controllers.

To verify and illustrate this new functionality, a new application test (SpringDocApp246Test) has been added. This test:
•Defines webhook components in two separate packages.
•Configures one package to be included and the other to be excluded.
•Asserts that the final OpenAPI document correctly contains only the webhooks from the scanned package.

Additionally, a new abstract base class, AbstractSpringDocV31Test, has been created to streamline the setup for OpenAPI 3.1 integration tests.

Fixes #3056

[Mattias-Sehlstedt]

Hi @zdary

I would suggested adding an application test to further illustrate the changed behavior. So something similar to this test, but that it explicitly covers how the new filtering works (the test produces and exposes a specification for the code, and the expected specification is then located in resources/results).

I am not affiliate with this project in any way, so only a suggestion rather than a review.

[zdary]

Hi @zdary

I would suggested adding an application test to further illustrate the changed behavior. So something similar to this test, but that it explicitly covers how the new filtering works (the test produces and exposes a specification for the code, and the expected specification is then located in resources/results).

I am not affiliate with this project in any way, so only a suggestion rather than a review.

good point, I have added the tests to cover the filtering. thank you