chore(m365): enhance metadata for exchange service

[puchy22]

Context

Updating m365 exchange service metadata to conform with the new standardized metadata format used across Prowler checks, defined in #8411.

Description

This PR updates all metadata files for M365 Exchange checks to adapt to the new metadata format. The changes ensure consistency with the metadata structure being adopted across all Prowler services. The modified checks are:

• exchange_external_email_tagging_enabled
• exchange_mailbox_audit_bypass_disabled
• exchange_mailbox_policy_additional_storage_restricted
• exchange_organization_mailbox_auditing_enabled
• exchange_organization_mailtips_enabled
• exchange_organization_modern_authentication_enabled
• exchange_roles_assignment_policy_addins_disabled
• exchange_transport_config_smtp_auth_disabled
• exchange_transport_rules_mail_forwarding_disabled
• exchange_transport_rules_whitelist_disabled
• exchange_user_mailbox_auditing_enabled

Checklist

• Are there new checks included in this PR? No
  • If so, do we need to update permissions for the provider? No.
• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md
• Ensure new entries are added to CHANGELOG.md, if applicable.

API

• Verify if API specs need to be regenerated.
• Check if version updates are required (e.g., specs, Poetry, etc.).
• Ensure new entries are added to CHANGELOG.md, if applicable.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

✅ Conflict Markers Resolved

All conflict markers have been successfully resolved in this pull request.

[github-actions]

🔒 Container Security Scan

Image: prowler:bd637ba
Last scan: 2025-12-23 20:12:17 UTC

📊 Vulnerability Summary

Severity	Count
🔴 Critical	3
Total	3

3 package(s) affected

⚠️ Action Required

Critical severity vulnerabilities detected. These should be addressed before merging:

• Review the detailed scan results
• Update affected packages to patched versions
• Consider using a different base image if updates are unavailable

---

📋 Resources:

• Download full report (see artifacts)
• View in Security tab
• Scanned with Trivy