Add custom AWS logs integration for both aws-s3 input and aws-cloudwatch input

[kaiyan-sheng]

What does this PR do?

In the AWS package, we have data streams to parse and ingest several service logs, such as s3access, cloudtrail, vpcflow and etc. This PR is to add the raw s3 input into the AWS package as an option when the specific type of service log is not supported in its own data stream.

We decide to create a separate package called Custom AWS Logs in integrations and add both aws-s3 input and aws-cloudwatch input options in there. This way, it's aligned with custom logs input, custom TCP/UDP logs input and etc.

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.

How to test this PR locally

1. Setup s3access logs to send to an S3 bucket
2. Create an SQS and enable notification for new objects in S3
3. On the Integrations page, find AWS S3 and add it
4. Setup for S3 logs as below:

Related issues

#711

[andrewkroh]

Good idea to have a more generic integration for S3.

[kaiyan-sheng]

@andrewkroh Thank you for the review! Sorry I just got back to this and addressed your comments.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-02-08T23:13:17.214+0000

• Duration: 16 min 23 sec

Test stats 🧪

Test	Results
Failed	0
Passed	8
Skipped	0
Total	8

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.