Bug - Update optimization workflow to automatically push changes to release branch through a PR

[IsraelleHub]

The current Optimaze images workflow is trying to directly push changes to the release/vx.x.x branch, which is being rejected by the protected branch settings, as indicated by this error: "remote: - Changes must be made through a pull request."
A solution will be to:
[ ] modify Optimization workflow to create a pull request (PR) for the optimized images.
This will allow the changes to go through the proper review process.
[ ] After observing the behavior for some time, we can now allow it to push changes directly to release/cx.x.x branch

[IsraelleHub]

Holding off on this ticket since VA is working on revamping branch protection rules.
They rolled it out recently and it broke our release a bit, so they pulled it back until they can plan better

[IsraelleHub]

Note: At testing phase - PR URL is empty . Example

• I created a branch from develop and put it as a base branch in this workflow: It didn't trigger the optimize workflow giving that I haven't merge my branch into develop yet
• Since it won't create a PR if there are no changes. I created an empty text file and I push it. same result with empty PR url
• Next step is to test on a more realistic branch release/v0.0.0. if you keep it local and don’t push it up to the repo it’s fine, but if you do it will trigger the release branch workflow unless it is disabled
• Next will be to try using the github cli to create PR: Docs
• Also if we could temporarily give that test branch the same branch protection as the release/* branches for testing purposes, that's will be nice. We will try this out after VA is done revamping the branch protection rules.