firehose integration should support firehose

[hrai-nr]

This PR will handle following two scenarios:

1. If user is passing value of parameter StoreNRLicenseKeyInSecretManager as true , the LicenseKey will be stored in secret manager and will be used from there.
2. There are few parameters which we are using for entity synthesis, if user passes those value as key in common attribute, we will ignore the values passed by user and use those values which are needed for Entity Synthesis.

Testing Done:

1. Select StoreNRLicenseKeyInSecretManager as true and see if the secret are getting saved in secret manager and then used from there, the logs should flow in new relic in this scenario.
2. Select StoreNRLicenseKeyInSecretManager as false, create stack, see the delivery stream, it should use API Key for authentication, check if logs are flowing in new relic.
3. Attribute related testing: Tested by passing attributes which are used for Entity Synthesis, these attributes are not getting overriden.

Ref:
1.https://docs.aws.amazon.com/firehose/latest/dev/secrets-manager-whats-secret.html
5.https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-kinesisfirehose-deliverystream-secretsmanagerconfiguration.html
6.hashicorp/terraform-provider-aws#38210

[nr-rkallempudi]

@hrai-nr
Is this tested with enabling/disabling secret manager? also what about QC with attribute overriding?

Can you add some tests you have done in PR description

[ahegdeNR]

@hrai-nr if ShouldCreateSecret is false then does it actually create secret manager but kept disabled?

[hrai-nr]

No, in case ShouldCreateSecret is false, it will use LicenseKey by storing it in the delivery stream.

[ahegdeNR]

requested changes