Error Occurs When usageLimits Are Null/Empty, and usageLimits Should Be Optional

[javiercavlop]

Description:

• Problem: An error is triggered whenever the usageLimits field is null or empty by the Pricing2Yaml parser. This behavior causes issues for pricings that do not require any usage limits, making the field unnecessarily mandatory.

• Expected Behavior: The usageLimits field should be treated as optional, allowing for pricing configurations that do not include usage limits.

Suggestions:

1. Fix Error Handling: Update the system to handle null or empty usageLimits gracefully without triggering errors (and handle the related errors properly).

2. Make usageLimits Optional: Adjust the schema or validation logic to treat usageLimits as an optional field, supporting pricing configurations without limits.