add guardduty permissions and update trust policy for MemberInfrastructureAccess role

[Khatraf]

A reference to the issue / Description of it

#8050

How does this PR fix the problem?

This PR updates the MemberInfrastructureAccess IAM role to include:

• Trust policy for `malware-protection-plan.guardduty.amazonaws.com.
• Permissions to create and manage GuardDuty malware protection plans for S3.

The role already has permissions for:
EventBridge Management: Managing rules and targets specific to GuardDuty operations.
S3 Access: Accessing objects, managing bucket notifications, and handling validation objects for scanning. But also tagging so post-scan it will show if threat was found/not found.
KMS: for decryption

More detailed information can be found here: https://docs.aws.amazon.com/guardduty/latest/ug/malware-protection-s3-iam-policy-prerequisite.html

How has this been tested?

Please describe the tests that you ran and provide instructions to reproduce.

{Please write here}

Deployment Plan / Instructions

Will this deployment impact the platform and / or services on it?

{Please write here}

Checklist (check x in [ ] of list items)

• I have performed a self-review of my own code
• All checks have passed
• I have made corresponding changes to the documentation
• Plan and discussed how it should be deployed to PROD (If needed)

Additional comments (if any)

{Please write here}

[mikereiddigital]

lg2m

[ewastempel]

Suggested change

	statement {
	statement {

[ewastempel]

Looks like what we agreed on, there is just some funny indentation I suggested to change.

[ewastempel]

LGTM