E2E test cases for firehose

[hrai-nr]

This PR is raised for validating end to end test cases for firehose. Here are the cases we are validating:

1. Firehose stack is deployed with single cloudwatch trigger. Created a log event and validated that logs are flowing to New Relic successfully.
2. Firehose is deployed with single cloudwatch trigger with filter pattern present. Then validated the below 2 cases:

• When data is added with the filter pattern firehose reads that data and pushes to New Relic. Validated that the log exist in new Relic
• When data is added without the filter pattern firehose doesn’t push anything to New Relic. Validated that the log does not exist in new Relic

3. Firehose is deployed with single cloudwatch trigger with invalid cloudwatch log group name. Validate that cloudwatch trigger is not created. But firehose stack and firehose delivery stream is created.
4. For the logs that are flown in NewRelic we are validating common attributes as well as entity synthesis parameters.

[ahegdeNR]

Nit: Please make e2e tests mandatory only for merges and not pull requests. To fix this create different rule sets for develop and main branch instead of clubbing them. And add e2e tests as mandatory step only for main. Approved

[maya-jha]

how did you test this?

[hrai-nr]

how did you test this?

To test this, I am creating the PR with :
on:
pull_request:
branches:
- main
- develop

  and then once everything is working fine adding one more commit to change the  pull_request to push

[maya-jha]

Validate whether tests are run before merging or after merging.