Provide a property to remove unused components

[long-eared-owl]

I would love if any unused components like unused schemas could be removed automatically via a property

Property for unused schema removal:
mp.openapi.extensions.smallrye.remove-unused-schemas.enable=true

Proposed property for unused components removal:
mp.openapi.extensions.smallrye.remove-unused-components.enable=true

it could also be more specific
e.g.
mp.openapi.extensions.smallrye.remove-unused-schemas.enable=true
mp.openapi.extensions.smallrye.remove-unused-responses.enable=true
mp.openapi.extensions.smallrye.remove-unused-parameters.enable=true
mp.openapi.extensions.smallrye.remove-unused-examples.enable=true
mp.openapi.extensions.smallrye.remove-unused-request-bodies.enable=true
mp.openapi.extensions.smallrye.remove-unused-headers.enable=true
mp.openapi.extensions.smallrye.remove-unused-security-schemas.enable=true
mp.openapi.extensions.smallrye.remove-unused-links.enable=true
mp.openapi.extensions.smallrye.remove-unused-callbacks.enable=true
mp.openapi.extensions.smallrye.remove-unused-path-items.enable=true

Though it would be awesome to be able to remove more components than just duplicate schemas form the result.
We currently have this problem with unused examples.
We provode a common static openapi.json providing large componens/examples.
They will be used by to create two different openapi files (openapi-read.json and openapi-write.json).
The openapi-read.json would not need the examples defined for openapi-write.json.

Similar to #1183

[MikeEdgar]

Thanks for the issue, good idea. Maybe it could be consolidated in a single configuration property:

# deprecated
mp.openapi.extensions.smallrye.remove-unused-schemas.enable=true

# new way with list of keys under `#/components`
mp.openapi.extensions.smallrye.remove-unused-components=schemas,responses,parameters,headers

[long-eared-owl]

Even better. Amazing. 👍