chore(aws): enhance metadata for glue service

[puchy22]

Context

Updating aws glue 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 AWS Glue 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:

• glue_data_catalogs_connection_passwords_encryption_enabled
• glue_data_catalogs_metadata_encryption_enabled
• glue_data_catalogs_not_publicly_accessible
• glue_database_connections_ssl_enabled
• glue_development_endpoints_cloudwatch_logs_encryption_enabled
• glue_development_endpoints_job_bookmark_encryption_enabled
• glue_development_endpoints_s3_encryption_enabled
• glue_etl_jobs_amazon_s3_encryption_enabled
• glue_etl_jobs_cloudwatch_logs_encryption_enabled
• glue_etl_jobs_job_bookmark_encryption_enabled
• glue_etl_jobs_logging_enabled
• glue_ml_transform_encrypted_at_rest

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]

✅ Conflict Markers Resolved

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

[github-actions]

✅ All necessary CHANGELOG.md files have been updated.

[github-actions]

🔒 Container Security Scan

Image: prowler:eadda7e
Last scan: 2025-12-15 11:02:49 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 3.76%. Comparing base (2b4b23c) to head (497d6c1).
⚠️ Report is 2 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (2b4b23c) and HEAD (497d6c1). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (2b4b23c)	HEAD (497d6c1)
api	1	0

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #9258       +/-   ##
==========================================
- Coverage   92.43%   3.76%   -88.68%     
==========================================
  Files         159     830      +671     
  Lines       22675   23443      +768     
==========================================
- Hits        20960     882    -20078     
- Misses       1715   22561    +20846     

Flag	Coverage Δ
api	?
prowler-py3.10-aws	3.76% <ø> (?)
prowler-py3.11-aws	3.76% <ø> (?)
prowler-py3.12-aws	3.76% <ø> (?)
prowler-py3.9-aws	3.76% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
prowler	3.76% <ø> (∅)
api	∅ <ø> (∅)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.