Added SHA384 hashing to event ID format

[girodav]

What does this PR do?

This PR changes the event ID format to use a SHA3_384 hash of the AWS-related information we use to generate the ID (e.g S3 bucket name, kinesis stream name, etc)

Why is it important?

Some AWS resources allows to have very long names, sometimes equal to the maximum allowed ID length in Elasticsearch (e.g Cloudwatch allows log group names of 512 characters). Since we use this information to generate the ID, as is, we can generate IDs that are effectively bigger than 512 bytes (ref: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-id-field.html)

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.md

Related issues

• Relates to Refactor _id generation #212

[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: 2023-02-03T04:37:52.467+0000

• Duration: 43 min 32 sec

Test stats 🧪

Test	Results
Failed	0
Passed	423
Skipped	0
Total	423

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (5/5)	💚
Files	100.0% (30/30)	💚
Classes	100.0% (30/30)	💚
Lines	100.0% (2073/2073)	💚
Conditionals	100.0% (720/720)	💚

[aspacca]

🥇