Fix --github-image-id flag for Breeze (#18882)

[potiuk]

When we moved to github registry, the --github-image-id flag was
broken as it had pulled the "latest" image when run right after
pulling the tagged image (and it run that image instead).

This change fixes it and uses GITHUB_PULL_IMAGE_TAG (latest if not
specified) everywhere where the image is used for running.
This flag is not persistent so it is not persistent.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[potiuk]

Another attempt to do #18882

This time I am testing it also in my fork for main changes:

Building Images: https://github.com/potiuk/airflow/actions/runs/1337712852
Tests: https://github.com/potiuk/airflow/actions/runs/1337712854

Attempt 2:

Build image: https://github.com/potiuk/airflow/actions/runs/1337812489
Tests: https://github.com/potiuk/airflow/actions/runs/1337812485

[potiuk]

Looks good this time @jedcunningham > there are failures in my fork but they are unrelated

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.