feat: Add sriov-network-operator-config-daemon-stig-fips image into release.yaml

[e0ne]

…elease.yaml

[coveralls]

Pull Request Test Coverage Report for Build 19070837746

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 57 unchanged lines in 4 files lost coverage.
• Overall coverage increased (+0.2%) to 62.058%

---

Files with Coverage Reduction	New Missed Lines	%
controllers/macvlannetwork_controller.go	2	86.25%
pkg/state/state_ipoib_network.go	4	75.24%
controllers/ipoibnetwork_controller.go	7	77.38%
controllers/nicclusterpolicy_controller.go	44	78.07%

Totals
Change from base Build 19034402612:	0.2%
Covered Lines:	4143
Relevant Lines:	6676

---

💛 - Coveralls

[almaslennikov]

The -stig-fips version tag will get overwritten by https://github.com/Mellanox/network-operator/blob/master/.github/workflows/release.yaml#L253
I suggest we add a stig-fips flag here in the release.yaml and handle it in the release workflow

[almaslennikov]

We can check for this flag like we do for helm chart: https://github.com/Mellanox/network-operator/blob/master/.github/workflows/release.yaml#L262
Here we need to also export the tag for stig-fips flavor: https://github.com/Mellanox/network-operator/blob/master/.github/workflows/release.yaml#L36

[maze88]

For consistency - in several of our internal CI jobs (e.g. NGC promotion pipeline), we include logic for handling such StigFips or "-stig-fips" variants.