Generate path paramaters optimistically for flaky schemas

[ViktorPontinen]

Description

We have cases where our automatically generated OpenAPI schemas are missing proper path parameter definitions. It would be useful to have an escape hatch for these kind of flaky schemas. Where resolving the issue at the root might not be feasable or resource intensive.

Proposal

My suggestion is to allow an escape hatch for these kind of flaky schemas, using an option --generate-path-params that can be passed to the CLI. This option would enable the library to automatically extract path param keys from the url and add them to the generated paths.
This should not break anything else and not affect overall functionality, except for those that need it.

I understand this might be against the philosophy of this library. So please give feedback on if you think this is reasonable or not.

Extra

• I’m willing to open a PR (see CONTRIBUTING.md)

[ViktorPontinen]

PR for suggested changes: #2102