Allow for custom CA cert path with BITWARDEN_APP_CACERTS env var

[Radical-Egg]

🎟️ Tracking

Hi again,

This PR goes along with #111

📔 Objective

It would be helpful if an environment variable could be set to override the current default path for CA certificates. This would allow us to set BITWARDEN_APP_CACERTS to a common location like /etc/pki/tls/ca-bundle.crt or /etc/ssl/certs/ca-certificates.crt instead of a manual copy/symlink of CA certs to $SPLUNK_HOME/etc/auth/bitwarden_event_logs_cacerts.pem. With or without this change, it would also be helpful to document where to put custom CA certificates in the initial setup instructions or a debug statement in the logs to set the environment variable and/or check the default path $SPLUNK_HOME/etc/auth/bitwarden_event_logs_cacerts.pem.

Thanks for taking a look, I appreciate it!

⏰ 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

[eliykat]

Thanks for the PR, this makes sense to me. It was also an issue I ran into when setting up a local server.

Once this is merged I'll let our docs team know.

[vincentsalucci]

Internal tracking: PM-26199

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Checkmarx One – Scan Summary & Details – e0911dce-3bf6-44d8-8825-17800fe37b22

Great job! No new security vulnerabilities introduced in this pull request