[aws_cloudwatch_input_otel] add recently_active option

[jakubgalecki0]

Proposed commit message

Add recently_active option to awscloudwatch receiver config (elastic/opentelemetry-collector-contrib#19)

    ? awscloudwatch/otelcol-aws-lambda/....
    :   credentials_provider: awscredentialsprovider/...
        metrics:
            collection_interval: 1m
            delay: 5m
            discovery:
                filters:
                    namespace: AWS/Lambda
                limit: 100
                recently_active: true <<<
                stats:
                    - Maximum
                    - Average
                    - Sum
            period: 1m
        region: us-east-1
    ? awscloudwatch/otelcol-aws-rds/....
    :   credentials_provider: awscredentialsprovider/...
        metrics:
            collection_interval: 1m
            delay: 5m
            discovery:
                filters:
                    namespace: AWS/RDS
                limit: 100
                recently_active: true  <<<
                stats:
                    - Average
                    - Maximum
            period: 1m
        region: us-east-1
    ? awscloudwatch/otelcol-aws-sqs/....
    :   credentials_provider: awscredentialsprovider/...
        metrics:
            collection_interval: 1m
            delay: 5m
            discovery:
                filters:
                    namespace: AWS/SQS
                limit: 100
                recently_active: true  <<< 
                stats:
                    - Maximum
                    - Sum
            period: 1m

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

[elastic-vault-github-plugin-prod]

✅ All changelog entries have the correct PR link.

[infra-vault-gh-plugin-prod]

💚 Build Succeeded

• Buildkite Build
• Commit: e683437

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[elastic-vault-github-plugin-prod]

Package aws_cloudwatch_input_otel - 0.4.0 containing this change is available at https://epr.elastic.co/package/aws_cloudwatch_input_otel/0.4.0/