Support for schema properties named after JS reserved name

[timotheeguerin]

Right now having an openapi spec with a schema having a property named with values already used by JS objects causes collision error.

Keywords:

• [ ] toString #3530
• [ ] constructor
• [ ] call

Workaround:

Rename the property and use x-ms-client-name

{
 "toString": { ... }

->

{
  "toStringProp": { 
    "x-ms-client-name": "toString", ...
  }
}

[timotheeguerin]

Check if it fails correctly and close as by design. Workaround can be used if really on purpose.