build(docker): Push websocket image

[Yann-J]

SUMMARY

This PR is a followup to #21954 which was missing the step to actually push the freshly-built superset-websocket image to Docker hub.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

This can only be tested after merge, since the publication step is only run on master. After successful merge, we should see an apache/superset-websocket image in Docker hub, with the same tags as the main image.

ADDITIONAL INFORMATION

• Has associated issue: Publish websocket container #22126
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[craig-rueda]

LGTM!

[Yann-J]

Thanks @craig-rueda !

I see the build was successful, and the push was started off as expected, but then rejected by Docker Hub.

I think someone needs to just create the project in Docker Hub to unblock this - although I cannot be certain. In any case it's definitely something on Docker Hub side, which I don't think external contributors like me can fix...

[michael-s-molina]

@craig-rueda It seems the docker build step is failing on all master commits after this PR. Can you take a look?