feat: move supersetbot out of repo

[mistercrunch]

This PR

• moves supersetbot out of here and onto here https://github.com/apache-superset/supersetbot
• improves the GHA to set it up

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.72%. Comparing base (5b1d6b2) to head (a7c6276).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #27647      +/-   ##
==========================================
+ Coverage   67.38%   69.72%   +2.33%     
==========================================
  Files        1920     1920              
  Lines       75242    75242              
  Branches     8423     8423              
==========================================
+ Hits        50705    52461    +1756     
+ Misses      22476    20720    -1756     
  Partials     2061     2061              

Flag	Coverage Δ
mysql	77.88% <ø> (?)
postgres	77.99% <ø> (ø)
python	82.91% <ø> (+4.83%)	⬆️
sqlite	77.43% <ø> (ø)
unit	56.78% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rusackas]

Just curious, is this out of necessity, or just easier to work on it? It might be nice to move it back into Superset/ASF control once the dust settles if it's just to make it easier to get things spun up and tested for a while.

[mistercrunch]

Yes the main reason is it doesn't require the same level of scrutiny and rigor as the main repo, and it can have it's own CI/release cycles/tests, .

[rusackas]

Sounds reasonable... perhaps one day it can make a grand homecoming or something. I think the main thing is we need docs on the wiki so we can evangelize its use.

[mistercrunch]

Right, it can always move back here once things settle.