chore: move backend under superset-backend

[villebro]

SUMMARY

WIP

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

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

[korbit-ai]

Review by Korbit AI

Korbit automatically attempts to detect when you fix issues in new commits.

Category	Issue	Status
	Missing directory existence check ▹ view	🧠 Not in standard

Files scanned

​

Due to the exceptionally large size of this PR, I've limited my review to the following files:

File Path	Reviewed
superset-backend/setup.py	✅
.github/workflows/bashlib.sh	✅

Explore our documentation to understand the languages and file types we support and the files we ignore.

Check out our docs on how you can make Korbit work best for you and your team.

Loving Korbit!? Share us on LinkedIn Reddit and X

[mistercrunch]

Nice to see this! Wondering if you should take one step further and move to superset-backend/app/, assuming will be a need for things like superset-backend/extension-sdk/, superset-backend/data-access-layer/, all depending on something like superset-backend/core/ (?)

Oh also... now that there will be no pyproject.toml in the root (currently that makes it clear that it's a python project primarily and that you can pip install apache-superset), I'm wondering if we should have a Code Orientation section at the bottom of the readme giving pointers to important places across the monorepo.