Fix Node deprecations and dynamic secret key extraction

[baraka-akeyless]

Summary

• Replace akeyless-cloud-id / AWS SDK v2 with a local cloud-id helper using AWS SDK v3 credential providers + aws4, and move CI/workflows to Node 24 / actions/checkout@v5 / setup-node@v5.
• Fix dynamic secret key extraction for object-shaped API responses (e.g. GitHub DS { "token": "..." }) so output-name + key: token works instead of failing with Failed to export dynamic secret.
• Bump release version to v1.1.7.

Dynamic secrets usage (after this fix)

dynamic-secrets: |
  - name: "/cloud/github/github-ds"
    output-name: "TOKEN"
    key: "token"

That exports just the token string under TOKEN.

Note: with parse-json-secrets: true and no key, fields are still expanded with a path/prefix-json-secrets prefix (same as static secrets); output-name applies when exporting a single value (with or without key).

Test plan

• npm test (32 tests, including new dynamic-secret object/key cases)
• npm run package rebuilt dist/
• CI: akeyless action code tests
• CI: Akeyless Github Action Tests (integration)
• Manual: fetch GitHub dynamic secret with key: token and output-name: TOKEN, confirm Authorization: Bearer $TOKEN works

Made with Cursor