fix(actions): remove outdated actions and update documentation accordingly

[cx-artur-ribeiro]

Reason for Proposed Changes

• Since the last Pull Request updating the CI, some actions were left untouched since they were not used. We are currently deprecating unused actions, as well as update any documentation that references those actions.

Proposed Changes

• Remove outdated actions:
  • release-docker-github-action.yaml: Updates docs/docker with new released version. Not used since 2022 and not updated as well. To remove this action, we need to remove the associated code related to this action (docs/docker);
  • update_software_versions.yaml: updates software versions for the new release on .github/scripts/update_versions/requirements.txt;
  • update-install-script.yaml: not used since 2021, only updates the install.sh script which is not used at the moment. The script in question does not exist as well, this action should have been deleted a long time ago with the deletion of the script;
  • release-nightly: we haven't used or released nightly versions in 2,5+ years, so we don't need this action at all;
  • realease.yaml: unused action, full commented, will be removed as well.
• Remove all KICS_BOT_PAT variable usage;
• Update python registry to echohq;
• Fix security vulnerabilities.

I submit this contribution under the Apache-2.0 license.

[stepsecurity-app]

✅ Resolved — a later workflow run passed this policy check.

Original alert (resolved)

Security Policy Alert: Secret Policy Violation

This workflow run has been blocked by StepSecurity's secrets policy because it accesses secrets and the workflow file differs from the default branch.

Secret references detected:

• secrets.ECHO_LIBRARIES_ACCESS_KEY at line 47
• secrets.KICS_BOT_PAT at line 102
• secrets.GITHUB_TOKEN at line 103

To approve this workflow, please add the workflows-approved label to this PR.

Note: The label must be added by someone other than the PR author (cx-artur-ribeiro) or automation bots to ensure proper security review.

After the label is added, you can re-run the blocked workflow to proceed.

This workflow will be automatically approved once merged into the default branch.

For more information, see StepSecurity's Secret Exfiltration Policy documentation.