chore(deployment tooling): Update Prowler API with rotating K8S access keys

[metahertz]

Context

newer versions of the kubernetes API do not allow long-lived/non-expiring tokens to be bound to a service account, while there are workarounds, certain clusters (Auto EKS from my current experience and others on the Community Slack) do now allow non-expiring tokens and force the TTL/Expiry down to a global value.

Solution here is the Kubernetes-documented way to access rotating service credentials, via a 'projected' volume type into a POD inside the k8s cluster; which will provide a mount with a rotating token for that service account.
Example Pod Snippet:

      volumes:
      - name: sa-token
        projected:
          sources:
          - serviceAccountToken:
              path: token
              expirationSeconds: 3600

This PR adds a simple deployment, running a pod, mounting the existing prowler prowler-ns/prowler-sa service account and a filesystem listener to auto update our Prowler API with any auth changes.

Description

See documentation in PR.

Checklist

• Are there new checks included in this PR? No
• [N/A] If so, do we need to update permissions for the provider? Please review this carefully.
• [NO - DISCUSS?] Review if the code is being covered by tests.
• [YES] Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• [NO] Review if backport is needed.
• [NO] Review if is needed to change the Readme.md

API

• [NO] Verify if API specs need to be regenerated.
• [NO] Check if version updates are required (e.g., specs, Poetry, etc.).
• [NO] 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.