ironbank: update the list of maintainers for the ironbank

[v1v]

Proposed commit message

Update the list of maintainers for the ironbank, so it reflects the new org.

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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

cd x-pack/metricbeat
mage package
make -C ironbank package
mage ironbank

Then you will see the .tar.gz in the build/distributions folder for each subscribed beat, and hardening_manifest.yaml will contain the new up-to-date list of maintainers

Related issues

#32251 was the initial implementation

Use cases

Screenshots

Logs

[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-08-16T14:39:52.959+0000

• Duration: 103 min 23 sec

Test stats 🧪

Test	Results
Failed	0
Passed	28120
Skipped	2015
Total	30135

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

@jlind23 @cmacknz , those users are the ones that will receive notifications regarding the Ironbank release process. You can include as many new maintainers as you wish.

I plan to merge this as soon as I get another approval.

[jlind23]

@v1v Just added my information to make sure Nassim is not the only one being pinged.