feat(openapi): support patternProperties

[fxalgrain]

Description

This PR solve #165 issue.

The idea is to transform the patternProperties into a valid OpenAPI definition. We lost the precision in public documentation but validation still done on server side

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

lgtm

[mcollina]

@climba03003

[climba03003]

Can you also change it on swagger side?

[coveralls]

Pull Request Test Coverage Report for Build 1583864045

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 12 of 12 (100.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 1572109812:	0.0%
Covered Lines:	628
Relevant Lines:	628

---

💛 - Coveralls

[fxalgrain]

I can do it but I m not a daily user of swagger specs.
Before do it, could you confirm me the following stuff:
It looks like we can apply the same code fix as additionalProperties exists too. https://github.com/OAI/OpenAPI-Specification/blob/main/versions/2.0.md#schemaObject
And after go in the code, I think we need update the resolveResponse and resolveBodyParams?

@climba03003 Sounds good for you?

[climba03003]

@climba03003 Sounds good for you?

Yes, you can apply the same fix.

[fxalgrain]

@climba03003 I did it, expecting as you wish :)

[climba03003]

LGTM.