feat: add new option and interface to allow customization of how model names are generated

[crtl]

Introduce ModelNameGeneratorInterface and wire it through ApiDocGenerator and ModelRegistry to allow customizing schema/model names.

• Add NoopModelNameGenerator as the default (BC-preserving) implementation
• Add GroupAppendingModelNameGenerator that appends sanitized, sorted group names to the short name
• Add configuration option models.model_name_generator (default: nelmio_api_doc.model_name_generator.default)
• Register services and aliases in config/services.php and wire via NelmioApiDocExtension
• Update docs with configuration examples and usage guidance
• Add tests for generators and update ModelRegistryTest to cover the integration

Description

This is my first PR, feedback is very welcome

Currently when using serialization groups with models the generated model names produce conflicts and are thus numberd.
Aside from being none descriptive the number assigned is just the first processed controller which uses the model.
When refactoring code and thus changing the order the controllers are processed the numbering can change.

This becomes especially problemativ when using the json output to generate sdk clients using various tools.

As a solution i have provided a new interface ModelNameGeneratorInterface which can be passed to models.model_name_generator in configuration to allow customization of how model names are generated.
By default a noop subscriber is used to maintain backwards compatibility but a nelmio_api_doc.model_name_generator.group_appending is provided too which can be used to include serialization groups in generated Model name, elminiating most of possible conflicts.

For example a model User is used with groups ["public-read"] will produce model name User_publicRead.

Should there still be a conflict it will fall back to the default numbering logic.

Closes:

• Groups is not used for Model naming in array property of object #1787
• Allow model alternative names inside the model class #1730 (potentially)

What type of PR is this? (check all applicable)

• Bug Fix
• Feature
• Refactor
• Deprecation
• Breaking Change
• Documentation Update
• CI

Checklist

• I have made corresponding changes to the documentation (docs/)

[github-actions]

This PR has been marked as stale because it has not had any activity for 60 days. Remove stale label or comment to prevent this from being closed in 60 days.