Fix aws.cloudtrail.request_id parsing

[kaiyan-sheng]

What does this PR do?

This PR fixes a parsing pipeline typo in the AWS Cloudtrail logs. The same bug will be fixed in Filebeat with elastic/beats#33143.

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.

[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-09-22T21:49:22.691+0000

• Duration: 35 min 5 sec

Test stats 🧪

Test	Results
Failed	0
Passed	162
Skipped	2
Total	164

🤖 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]

🚀 Benchmarks report

Package aws 👍(8) 💚(4) 💔(1)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
route53_resolver_logs	6493.51	5464.48	-1029.03 (-15.85%)	💔

To see the full report comment with /test benchmark fullreport

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (13/13)	💚
Files	92.857% (13/14)	👎 -4.493
Classes	92.857% (13/14)	👎 -4.493
Methods	84.232% (203/241)	👎 -5.636
Lines	95.697% (5204/5438)	👍 4.368
Conditionals	100.0% (0/0)	💚