Performance improvements (quick wins)

[moukoublen]

Summary of your changes

Screenshot/Data

Related Issues

Checklist

• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added the necessary README/documentation (if appropriate)

Introducing a new rule?

• [ ] Generate rule metadata using this script
• [ ] Add relevant unit tests
• [ ] Generate relevant rule templates using this script, and open a PR in elastic/packages/cloud_security_posture

[mergify[bot]]

This pull request does not have a backport label. Could you fix it @moukoublen? 🙏 To fixup this pull request, you need to add the backport labels for the needed branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major. NOTE: backport-v8.x has been added to help with the transition to the new branch 8.x.

[orestisfl]

Would be nice (outside of this PR) to set some kind of continued benchmarking tool to compare our performance / memory usage for go benchmarks: https://github.com/benchmark-action/github-action-benchmark