fix: docker-compose up ModuleNotFoundError: {...} superset

[mistercrunch]

As reported here our Dockerfile is currently broken. Somehow the copy command was copying the superset/superset folder instead of superset/ in some setups.

[rusackas]

I have all the clueless questions about how it broke, why it worked before, and why more people aren't running into this, etc.

This looks like it'll copy in a lot more stuff, will that lead to any bloat/slowdown?

Otherwise this looks very stampable to me when it's ready for review.

[mistercrunch]

from my troubleshoot

• uv has some quirks around switching users
• docker cache works in mysterious ways, somehow my setup was working with what I assume was older docker cache that should have been validated (?)

Rolling back using uv in docker, tested it works from clean cache

[mistercrunch]

closing in favor of #31385