chore: add $or operator to the EventPattern interface

[b-dur]

This PR adds a missing $or comparison operator to the EventPattern interface. As describe in the doc the $or is not limited to only be on the leaf-node.

Before this change the TS compiler would throw Object literal may only specify known properties, and '$or' does not exist in type 'EventPattern' Error. By adding // @ts-ignore one could get ride of the TS error and the code/rule would work as expected.

With this change the TS compiler no longer raises this error and $or is an excepted property on the EventPattern interface.

Integration test was not run.

It is uncertain what prefix should have been used for this PR. Is Fix. more accurate?

---

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

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

[b-dur]

The error seeing now is:

 error JSII8002: Method and property (unless they are static readonly) names must use camelCase. Rename "aws-cdk-lib.aws_events.EventPattern.$or" to "or"

I wonder if there is a way to avoid this? Or can or be used instead of $or ?

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 564a335
• Result: FAILED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[kaizencc]

I see the docs that say "Comparison operators only work on leaf nodes, with the exception of $or and anything-but." so I'm willing to entertain this. This PR needs:

• the property can't be named $or. This really means 'anyOf' right? Lets name it that
• integ test demonstrating that we can use this property at the root level.

[aws-cdk-automation]

This PR has been in the BUILD FAILING state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week.

[aws-cdk-automation]

This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error.