feat(aws): add acmpca service and pqc key algorithm check - #11318

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/user-guide/cli/tutorials/configuration_file.mdx`:
- Line 58: The documentation entry for the
acmpca_certificate_authority_pqc_key_algorithm configuration parameter at line
58 is missing a Version Badge component that indicates when this feature was
introduced in Prowler. Add a Version Badge component to the documentation to
clearly specify the version when this new configurable check entry was
introduced, following the established pattern for new feature documentation in
the mdx file.

In
`@prowler/providers/aws/services/acmpca/acmpca_certificate_authority_pqc_key_algorithm/acmpca_certificate_authority_pqc_key_algorithm.py`:
- Line 19: The execute() method lacks a required Google-style docstring. Add a
docstring immediately after the method definition that describes the method's
purpose, notes that it takes no explicit parameters beyond self, and documents
that it returns a list of Check_Report_AWS findings. The docstring should be
concise and follow Google documentation conventions with sections for
description and Returns.

In `@prowler/providers/aws/services/acmpca/acmpca_service.py`:
- Around line 10-18: The ACMPCA class and its methods are missing required type
hints and Google-style docstrings. Add type hints to the __init__ method
(specifying the provider parameter type and return type) and the
_list_certificate_authorities method (specifying the regional_client parameter
type and return type). Add Google-style docstrings to the ACMPCA class
describing its purpose, the __init__ method describing initialization and
parameters, the _list_certificate_authorities method describing its
functionality, and the CertificateAuthority class (also mentioned at line 48-57)
describing its structure and attributes. Follow Google documentation style
format with proper sections for Args, Returns, and descriptions.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/user-guide/cli/tutorials/configuration_file.mdx`:
- Line 60: The VersionBadge component is currently placed inline within the
acmpca_certificate_authority_pqc_key_algorithm table cell, but according to the
style guidelines it must be removed from the table and placed on its own line
immediately after a section header or feature title instead. Remove the
VersionBadge component from the table row, then position it on its own line
after the appropriate section header with a blank line following it before the
table content begins.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/user-guide/cli/tutorials/configuration_file.mdx`:
- Line 63: The table row containing the
acmpca_certificate_authority_pqc_key_algorithm entry is positioned out of
alphabetical order in the configuration file table. Move this row from its
current location at line 63 to its correct alphabetical position, which should
be immediately after the acm_certificates_expiration_check row (around line 26)
to maintain the established alphabetical sorting by check name.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@docs/user-guide/cli/tutorials/configuration_file.mdx`:
- Line 19: The documentation for the
acmpca_certificate_authority_pqc_key_algorithm check is missing a
subsection-level Version Badge indicating when it was introduced in version
5.31.0. Add a VersionBadge component with version="5.31.0" immediately before
the table row containing the acmpca_certificate_authority_pqc_key_algorithm
check, or create a subsection header with the badge following the same pattern
used in other documentation files like prowler-app-lighthouse-multi-llm.mdx, to
ensure the badge clearly marks when this specific security check was added.