fix(install/docker): use zstd-baked image for building superset-frontend in containerized env

[hainenber]

fix(install/docker): use zstd-baked image for building superset-frontend in containerized environment

SUMMARY

Fixes #30206

It turns out that building superset-node in development's Docker Compose file doesn't use image baked with zstd. This PR fixes the issue by using zstd-baked image from existing Dockerfile.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Before

After

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

• Has associated issue:
• 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

[mistercrunch]

Hey, I have an alternate fix as bycatch as part of #30274. I think it's the proper solution, where docker-compose should be using the superset-node layer which insures more compatibility between the build process when building layers with the docker-compose environment.

It would be great to factor it out of my PR (as opposed to coupling it to the unrelated Slack avatar stuff). Feel free to copy/paste the solution from my PR here and I'll approve and merge.

[hainenber]

Hey, I have an alternate fix as bycatch as part of #30274. I think it's the proper solution, where docker-compose should be using the superset-node layer which insures more compatibility between the build process when building layers with the docker-compose environment.

It would be great to factor it out of my PR (as opposed to coupling it to the unrelated Slack avatar stuff). Feel free to copy/paste the solution from my PR here and I'll approve and merge.

Copy-pasted. The issue is still resolved after your alternate fix! :D