feat: remove unsupported array schema properties and add validation

[surendar-05]

Description

This PR addresses the issue with unsupported minItems and maxItems properties in array schemas that were causing API errors. Instead of allowing these properties to pass through to the API and fail, we now validate them early and provide a clear error message.

Changes

• Removed minItems and maxItems from ArraySchema interface
• Added validation to catch usage of these properties
• Updated documentation to clarify limitations
• Added test case for validation

Testing

• Added unit test for validation
• Manually tested with example usage
• Ran full test suite

Fixes #200

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[MarkDaoust]

Hi, thanks for taking the time to create a PR.

minItems and maxItems properties in array schemas that were causing API errors.

When was this? The API definitely supports this.

Here's a quick example in python:

https://colab.research.google.com/drive/1ffoMRvPzRUvnP8zuYHt6mqCH-u9-piid

This works:

{"items":{"type":"NUMBER"},"max_items":4,"min_items":3,"type":"ARRAY"}

The API is insensitive to snake_case vs camelCase.

So I don't think removing this is the right approach.