fix: bump click in setup.py and requirements.txt

[villebro]

CATEGORY

Choose one

• Bug Fix
• Enhancement (new features, refinement)
• Refactor
• Add tests
• Build / Development Environment
• Documentation

SUMMARY

As of #9277 , pip-tools was bumped to 4.5.1, which requires click>=7: link. This is currently at odds with setup.py, which requires click<7.0.0. This PR bumps click to the latest version, which seems to work well with Superset.

TEST PLAN

Tested locally + CI

REVIEWERS

@john-bodley

[mistercrunch]

The reason it was pinned is because click>=7 forces dashes in subcommands ie superset load-examples instead of superset load_examples.

It's better but disruptive... Will break dockers and helm charts everywhere. I wonder if there's a way to support both with click>=7

[mistercrunch]

Nice solution to support both fresh as of 19 days ago! pallets/click#1123 (comment)

[villebro]

Thanks for this @mistercrunch , I'll update accordingly!

[codecov-io]

Codecov Report

Merging #9299 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9299      +/-   ##
==========================================
+ Coverage    58.9%   58.93%   +0.03%     
==========================================
  Files         373      373              
  Lines       12026    12033       +7     
  Branches     2953     2955       +2     
==========================================
+ Hits         7084     7092       +8     
+ Misses       4763     4762       -1     
  Partials      179      179

Impacted Files	Coverage Δ
superset-frontend/src/components/Button.jsx	88.88% <0%> (ø)	⬆️
...end/src/SqlLab/components/RunQueryActionButton.jsx
...end/src/SqlLab/components/RunQueryActionButton.tsx	88% <0%> (ø)

---

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 0c8c4d6...b4a8f13. Read the comment docs.

[dpgaspar]

LGTM, not a big fan of keeping the _ but totally understand, for the sake of stability.
I propose to remove this on 1.0.0

[villebro]

Perhaps we should add a TODO to keep track of stuff that will get refactored for 1.0?