BRE-342 Implement retry mechanism with error handling to get secrets from KV

[urbinaalex17]

🎟️ Tracking

BRE-342

📔 Objective

Fix get-keyvault-secrets action intermittent failures by implementing retry mechanism with error handling to get secrets from Azure Key Vault.

📸 Screenshots

Known issues: https://github.com/bitwarden/server/actions/runs/11033476838/job/30644953330

In this execution we can clearly see that the retry mechanism was executed due to the execution time, 9 seconds compare to the 6 seconds when the step failed (RETRY_DELAY = 3000):

https://github.com/bitwarden/server/actions/runs/11167289676/job/31043388477

Multiple jobs were triggered:

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – 5e98459c-3a71-4108-922a-71707cdbce68

No New Or Fixed Issues Found

[vgrassia]

The PR body is missing all the information. Can you please fill it out?

[vgrassia]

I was able to test with debug and finally get an error that retried successfully. This will work as a temporary fix until we can move on from using Azure Key Vaults.