fix(dpp)!: data contract validation issues

[shumkov]

Issue being fixed or feature implemented

Revisit Data Contract validation logic to make sure we don't have any potential vulnerabilities and bugs.

What was done?

• Switched rs-jsonschema to the latest version of upstream instead of our forks. All required modifications were done there with additional fixes and optimizations.
• Mitigated ReDoS attack. Based on feat: configure patterns regex engine Stranger6667/jsonschema#487
• Removed unnecessary array-based rules from document meta schema since we do not support arrays for now (except byte arrays)
• Compile document schema after validation against meta schema (compilation is heavier)
• Removed unnecessary traversal validators since they are doing double work
• Fixed an error when use still can use arrays but they will be encoded as booleans
• Removed duplicated Value to JSON Value conversion

How Has This Been Tested?

With existing tests. Wrote unit tests for ByteArraay keyword.

Breaking Changes

Data Contract validation logic is changed so previously created blockchain data might not be valid.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone