fix: update init container config refs in primary spec

[immanuwell]

ApplyPrimaryConfigs rewrites ConfigMap/Secret refs in spec.Containers to use -primary copies, but skips spec.InitContainers entirely. GetTargetConfigs already tracks init container refs, so the primary copies get created, but the init containers in the primary deployment still point to the originals. Not great.

How to reproduce: deploy anything with an init container that pulls config from a ConfigMap or Secret via env/envFrom, let flagger init the primary, check the primary deployment spec - init containers still reference the original names.

Fix mirrors the existing containers loop for InitContainers. Also squashed a double-space typo in an error message while in the file.

Tests added to TestConfigTracker_ConfigMaps and TestConfigTracker_Secrets for both deployment and daemonset subtests.

[aryan9600]

lgtm - thank you for the fix! 🏅

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 30.08%. Comparing base (61582f7) to head (aecdbf4).
⚠️ Report is 4 commits behind head on main.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1925      +/-   ##
==========================================
+ Coverage   30.00%   30.08%   +0.08%     
==========================================
  Files         288      288              
  Lines       18455    18477      +22     
==========================================
+ Hits         5537     5559      +22     
  Misses      12189    12189              
  Partials      729      729              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.