Missing Docker Hub images for 4.1.0

[padbk]

Bug description

The Github Actions to upload the 4.1.0 release images to Docker Hub failed.
https://github.com/apache/superset/actions/runs/11826540775

It looks like this was due to the PR being incorrectly labelled.
https://github.com/apache/superset/actions/runs/11826540775/job/32952794218#step:9:41

Please can a new PR be made to ensure the images are pushed to Docker Hub.

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

Not applicable

Node version

Not applicable

Browser

Not applicable

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[janhoon]

docker tag for the 4.1.0 commit is available: https://hub.docker.com/layers/apache/superset/855f4c4897771cf454c8a0172eb21e47d13f3614/images/sha256-a64435896d2c21cb775a0e08035c68e64ed15cefea916a863ccf575b3babf5f0?context=explore

[sadpandajoe]

@padbk unsure why the docker image hasn't published? I see that 4.1.0rc4 was published fine and this is using the same SHA. May need someone with more knowledge of how our Docker pipeline works to take a look at it.

@michael-s-molina @mistercrunch any ideas? Wondering if this is something in the dockerfile in the branch or if it's an issue with the dockerfile in the master branch.