Add security schemes filter normalizer option (#23174)

* Implement `normalizer` for security schemes

* Continue development

* Implement new filter logic
Add test for it
Optimize old filter logic

* Add unit test on joint logic with `SET_BEARER_AUTH_FOR_NAME`

* Add docs

* Remove security schemes without marking them `x-internal`

* Clean up deleted security schemes references

* Discard unnecessary changes

* Fix typo

* Fix test

* Fix code review remarks

* Fix code review remark

* Fix code review remark

* Clean up callbacks and web hooks

* - Revert cleaning trailing white spaces from markdown file
- Make the changes backward compatible with custom filters
- Iterate over nested callbacks in path items

Author: limentas

docs/customization.md

@@ -754,6 +754,28 @@ Into this securityScheme:
       type: http
 ```
 
+- `SECURITY_SCHEMES_FILTER`
+
+The `SECURITY_SCHEMES_FILTER` parameter allows selective inclusion of API security schemes based on specific criteria. It removes security schemes that do **not** match the specified values, preventing them from being generated. All references to removed security schemes also deleted. Multiple filters can be separated by a semicolon.
+
+### Available Filters
+
+- **`key`**
+  When set to `key:api_key|http_bearer`, security schemes **not** matching `api_key` or `http_bearer` will be marked as internal (`x-internal: true`), and excluded from generation. Matching operations will have `x-internal: false`.
+
+- **`type`**
+  When set to `type:apiKey|http`, security schemes **not** using `apiKey` or `http` types will be marked as internal (`x-internal: true`), preventing their generation.
+
+### Example Usage
+
+```sh
+java -jar modules/openapi-generator-cli/target/openapi-generator-cli.jar generate \
+  -g java \
+  -i modules/openapi-generator/src/test/resources/3_0/petstore.yaml \
+  -o /tmp/java-okhttp/ \
+  --openapi-normalizer SECURITY_SCHEMES_FILTER="key:api_key|http_bearer ; type:oauth2"
+```
+
 - `SORT_MODEL_PROPERTIES`: When set to true, model properties will be sorted alphabetically by name. This ensures deterministic code generation output regardless of property ordering in the source spec.
 
 Example: