Add debug logging to bluegreen secrets injection path

[jonathonbyrdziak]

The previous debug logging was only added to the standard startContainers path, but release/bluegreen deployments use dockerUpWithSecrets instead. Logs the override contents, full docker command, and docker output.

Summary

Brief description of what this PR does.

Change Type

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Security fix (addresses a vulnerability)
• Documentation update
• Refactoring (no functional changes)

Changes Made

Testing

• I have tested this locally
• Existing functionality is not broken
• I have added/updated tests where applicable

Test Steps

1. ...
2. ...

Security Checklist

• No credentials, secrets, or API keys are committed
• Shell commands use escapeshellarg() for variable interpolation
• User input is validated and sanitized
• File operations validate paths stay within expected boundaries
• No debug code (var_dump, die, print_r) is included

SOC 2 Readiness

• Changes maintain audit trail (git history)
• Changes do not weaken access controls
• Changes do not expose confidential data
• Changes are documented (code comments, docs updates)
• N/A - Changes do not affect SOC 2 readiness

Related Issues

Closes #

Screenshots / Output

If applicable, include command output or screenshots.