fix: versions aren't pinned and pip-compile-validate doesn't detect dependency changes

[ofekisr]

SUMMARY

A better best practice is to put all project dependencies into the requirements file instead of setup.py
so adding a new dependency will Imply running pip-compile-multi.
When adding a new dependency into setup.py, pip-comiple-multi verify will not detect the change.
this PR try to prevent issues like #15527

Actually, I adapted the way pip-compile-multi did
and you can take another reference here: pip-compile-issue

another Important issue this PR fix is the packages that were in setup.py weren't pinned versions so the client who installs superset is not guaranteed the superset's dependencies will be the same when code was merged

note - before the commit, after moving the packages from setup.py I ran pip-compile-multi --no-upgrade to ensure
that all requirements files are ok

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Before opening the pr, I ran tox to ensure superset init is running to prove superset was installed ( successful running the ci inside tox)
you can try run tox by yourself
in addition, if the pr checks success, it mean nothing breaks

ADDITIONAL INFORMATION

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

[codecov]

Codecov Report

Merging #15573 (0a5c369) into master (9ed8ce5) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #15573   +/-   ##
=======================================
  Coverage   76.95%   76.95%           
=======================================
  Files         976      976           
  Lines       51326    51326           
  Branches     6912     6912           
=======================================
+ Hits        39498    39500    +2     
+ Misses      11607    11605    -2     
  Partials      221      221           

Flag	Coverage Δ
hive	81.30% <ø> (+<0.01%)	⬆️
javascript	71.40% <ø> (ø)
mysql	81.56% <ø> (+<0.01%)	⬆️
postgres	81.59% <ø> (+<0.01%)	⬆️
presto	81.29% <ø> (+<0.01%)	⬆️
python	82.12% <ø> (+<0.01%)	⬆️
sqlite	81.19% <ø> (+<0.01%)	⬆️

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

Impacted Files	Coverage Δ
superset/config.py	91.83% <0.00%> (+0.68%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9ed8ce5...0a5c369. Read the comment docs.

[john-bodley]

@ofekisr I don't believe this is the right approach, especially as we should strive to always ensure that all the dependencies are pinned. In #15574 I've added instructions regarding how and when users should recreate the dependencies.