(1) Bump awsfindingsmanagerlib to 1.2.0

• Updates default SecurityHub filter to fix issues with SecurityHub Integration findings support.
• Adjusted filtering logic to align with SecurityHub filtering: When both match_on options: tags and resource_id_regexps are specified, they are now combined using an AND condition instead of an OR condition.
• Introduce pagesize.

(2) Update the EventBridge rule for detecting Security Hub findings events, triggering the findings manager events lambda.

With the current filter structure, the support for SecurityHub integrations is not working.

• See: chore: updates default SecurityHub filter awsfindingsmanagerlib#26
• ComplianceStatus is not available in findings coming from integrated services such as GuardDuty and Inspector. This means that these findings are never returned and can't be suppressed.
• the final indicator that a finding that matches a suppression rule is still not suppressed is having WorkflowStatus equals NEW or NOTIFIED.

If the end user is using the jira integration nothing changes. The query then already includes all possible compliance statusses. If the end user is not using the jira integration now also compliance status PASSED and NOT_AVAILABLE are included, but this should not lead to many more invoications since the PASSED compliance status is not possible incombination with the NEW or NOTIFIED workflow status.

More information:
https://docs.aws.amazon.com/securityhub/1.0/APIReference/API_Workflow.html
https://docs.aws.amazon.com/securityhub/latest/userguide/controls-overall-status.html