Change `oneOf` to `anyOf` schema in owasp:api4:2019-string-restricted…

… and owasp:api4:2019-string-limit (stoplightio#43)

* Change `oneOf` to `anyOf` schema in owasp:api4:2019-string-restricted

The use of `oneOf` means that _only_ one of the schema constraints may be true,
but it is valid if two or more of the string schema constraint keywords
are present: `format`, `pattern`, `enum`, `const`.

* Change `oneOf` to `anyOf` schema in owasp:api4:2019-string-limit

Similar as with `2019-string-restricted`: the schema check should be
`anyOf` instead of `oneOf` in case a schema has more than one of the
keywords.

fix: do not warn if an operation defines 400 and 422 responses (stopl…

…ightio#38)

In `src/ruleset.ts`, change the `oneOf` schema to `anyOf`

Add test cases in `__tests__/owasp-api3-2019-define-error-validation.test.ts`:
  * test with both `400` and `422`
  * test with `4XX`

Co-authored-by: Nauman <mnaumanali94@gmail.com>

fix: tweak jsonpath expeession (stoplightio#40)

Update ruleset.ts

fix: module.exports present in ESM bundle (stoplightio#39)

test: coverd owasp:api6:2019-no-additionalProperties

feat: 500 messages now require content too

fix: update spectral functions and types

fix: improve the type array lookup (stoplightio#20)

feat: added owasp api limits for array, string and integer

Fixes stoplightio#16

perf: avoid .[ and just use [

related to performance discovery in IBM/openapi-validator#508