fix(ci): operator docker image artifactory push fix master branch

[ShubhamTatvamasi]

Signed-off-by: Shubham Tatvamasi shubhamtatvamasi@gmail.com

Summary

Same operator docker image CI fix.

https://github.com/magma/magma/pull/12377/files
https://github.com/magma/magma/pull/12412/files

Test Plan

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[Neudrino]

Is the PR intentionally against master?
I would expect for master the implementation is correct as is?

[ShubhamTatvamasi]

Is the PR intentionally against master? I would expect for master the implementation is correct as is?

Yes, we just don't want the same to happen with v1.8 that why this PR is needed.

[Neudrino]

Thanks for the explanation. And the restriction master or release branch will be the one from the workflow itself, such that we still avoid artifacts from PRs being pushed, afaiks.