* Handle relative urls for oauth authorization

The full URL is computed based on the current selected server
if a relative URL is used as authorizationUrl
or tokenUrl
Co-authored-by: NEliot Berriot <contact@eliotberriot.com>

fixes #6010
Co-authored-by: NAndrew Korshunov <andrew.korshunov@vizsc.com>

* this is a security fix

Co-authored-by: NRenovate Bot <bot@renovateapp.com>

Co-authored-by: NRenovate Bot <bot@renovateapp.com>

* Addendum to commit 65ea764b, in PR #6483

* response sample generation should take content type into consideration for stringify

Co-authored-by: NRenovate Bot <bot@renovateapp.com>

* Remove `npm install` from steps

Co-authored-by: NTheo Markovic <theodore.markovic@svenskaspel.se>

* When the media-type is changed, there is a new `onChangeMediaType` method to handle actions.
* If target schema properties key/value pairs does NOT equals current schema properties, clear the requestBodyValue, try-it-out request/response and validation params.
* If target schema properties key/value pairs DOES equals current schema properties, do not change or re-render schema properties
* oas3Selector `validateShallowRequired` now also validates required keys against target media-type

Fixes #6201, #6250, #6476

Co-authored-by: NRenovate Bot <bot@renovateapp.com>

* json schema array component should use schema to generate example in case of array items.
* empty value checkbox should be disabled if not empty => not empty list || not empty string
* curl should also check for not empty list