fix: use standalone ajv validation for model introspection schema

[AaronZyLee]

Description of changes

The direct Ajv dependency uses a a browser-unsafe eval which will cause a CSP(Content Security Policy) error during runtime. To resolve the issue, the following changes are made:

• Ajv is removed from dependency but added in dev dependency
• Use the standalone validation code generated by the Ajv library as suggested by the documentation to avoid the unsafe-val method to be used in browser.
  • https://ajv.js.org/standalone.html

Codegen Paramaters Changed or Added

Issue #, if available

Description of how you validated changes

Unit & E2E tests

Checklist

• [ ] PR description included
• [ ] yarn test passes
• [ ] Tests are changed or added
• [ ] Relevant documentation is changed or added (and PR referenced)
• [ ] Breaking changes to existing customers are released behind a feature flag or major version update
• [ ] Changes are tested using sample applications for all relevant platforms (iOS/android/flutter/Javascript) that use the feature added/modified
• [ ] Changes are tested on windows. Some Node functions (such as path) behave differently on windows.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.