[AWS] Support Cloudtrail tlsDetails field

[legoguy1000]

What does this PR do?

Parses tlsDetails field

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.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• closes Cloudtrail Ingest Pipeline: Does not parse tlsDetails structure #6300

Screenshots

[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-09-27T21:11:14.085+0000

• Duration: 55 min 47 sec

Test stats 🧪

Test	Results
Failed	0
Passed	212
Skipped	3
Total	215

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[legoguy1000]

bump

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!

[legoguy1000]

I haven't had the time to follow up on this or push it along. It should be GTG, might need a rebase.

…

On Tue, Sep 26, 2023 at 4:35 PM kaiyan-sheng ***@***.***> wrote: Reopened #6352 <#6352>. — Reply to this email directly, view it on GitHub <#6352 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADEEL4BKWPEDLFRV3LKUQO3X4NDAVANCNFSM6AAAAAAYSAILEM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[efd6]

/test

[efd6]

LGTM after the builder can be made to run and pass.

[kaiyan-sheng]

Thank you for making the change!

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (17/17)	💚
Files	94.444% (17/18)	👍
Classes	94.444% (17/18)	👍
Methods	86.047% (259/301)	👍 0.093
Lines	86.062% (7558/8782)	👍 0.024
Conditionals	100.0% (0/0)	💚

[efd6]

Still LGTM

[elasticmachine]

Package aws - 2.5.0 containing this change is available at https://epr.elastic.co/search?package=aws