chore(CI): add a workflow to push multiubuntu image on any change

[Manik2708]

Purpose of PR?:

Fixes #1876

Does this PR introduce a breaking change? No

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[Manik2708]

@rksharma95 @Aryan-sharma11 Please review this, as the previous PR had to closed due to uncertain reasons!

[Manik2708]

@rksharma95 @Aryan-sharma11 go-vuln is asking for upgrading go from 1.23.5 to 1.23.6

[rksharma95]

@rksharma95 @Aryan-sharma11 go-vuln is asking for upgrading go from 1.23.5 to 1.23.6

Let's upgrade to 1.23.6

[Manik2708]

@rksharma95 That again might lead to snyk failures, should I proceed forward?

[rksharma95]

@rksharma95 That again might lead to snyk failures, should I proceed forward?

snyk failure can be ignored if it's due to version support issue. You can proceed with upgrade.

[Manik2708]

@rksharma95 Upgraded to 1.23.6, please review

[rksharma95]

LGTM 👍

[rootxrishabh]

LGTM 🚀

[Manik2708]

@rksharma95 @Aryan-sharma11 @rootxrishabh I have changed the ci-test-ubi-image.yml. Please review! Should I introduce a dummy change (which would be reverted when this PR will become ready to merge) to test the CI?

[rksharma95]

@rksharma95 @Aryan-sharma11 @rootxrishabh I have changed the ci-test-ubi-image.yml. Please review! Should I introduce a dummy change (which would be reverted when this PR will become ready to merge) to test the CI?

Not needed.