Add aws_guardduty_malware_scan_settings resource

[twelsh-aw]

Description

Adds aws_guardduty_malware_scan_settings resource. This allows configuring scan criteria (tag filtering) and volume retention policies for EC2 malware scanning.

I tried my best to make it line up with the API schema (it's a little funky), but it's not one-to-one so custom flatten/expand functions are needed

Relations

Closes #33979

References

• https://docs.aws.amazon.com/guardduty/latest/ug/malware-protection-customizations.html
• https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateMalwareScanSettings.html

Output from Acceptance Testing

╰─ make testacc TESTS=TestAccGuardDutyMalwareScanSettings PKG=guardduty
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.5 test ./internal/service/guardduty/... -v -count 1 -parallel 20 -run='TestAccGuardDutyMalwareScanSettings'  -timeout 360m -vet=off
2025/03/01 22:08:18 Initializing Terraform AWS Provider...
=== RUN   TestAccGuardDutyMalwareScanSettings_basic
--- PASS: TestAccGuardDutyMalwareScanSettings_basic (26.74s)
=== RUN   TestAccGuardDutyMalwareScanSettings_scanResourceCriteria
--- PASS: TestAccGuardDutyMalwareScanSettings_scanResourceCriteria (48.52s)
=== RUN   TestAccGuardDutyMalwareScanSettings_disappears
--- PASS: TestAccGuardDutyMalwareScanSettings_disappears (13.70s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/guardduty  95.355s
...

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.