MNT: Drop Python 3.7 support

[pllim]

Description

MNT: Drop Python 3.7 support to be consistent with upstream (astropy, regions, etc).

TST: Clean up cron job workflow; it is unnecessarily complicated.

This is required for:

• Translator for regions and photutils #1138

Checklist for package maintainer(s)

This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.

• Are two approvals required? Branch protection rule does not check for the second approval. If a second approval is not necessary, please apply the trivial label.
• Do the proposed changes actually accomplish desired goals? Also manually run the affected example notebooks, if necessary.
• Do the proposed changes follow the STScI Style Guides?
• Are tests added/updated as required? If so, do they follow the STScI Style Guides?
• Are docs added/updated as required? If so, do they follow the STScI Style Guides?
• Did the CI pass? If not, are the failures related?
• Is a change log needed? If yes, is it added to CHANGES.rst?
• Is a milestone set? Milestone is only currently required for PRs related to Imviz MVP.
• After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

[pllim]

Ignore the OS X - Python 3.7 Expected — Waiting for status to be reported status (and so on). I need to update branch protection rules after this is merged. So that means this PR needs admin rights to merge (either @rosteen or myself can do it).

[codecov]

Codecov Report

Merging #1145 (3a4cd8c) into main (b2e6c8d) will increase coverage by 0.02%.
The diff coverage is n/a.

❗ Current head 3a4cd8c differs from pull request most recent head e0f639f. Consider uploading reports for the commit e0f639f to get more accurate results

@@            Coverage Diff             @@
##             main    #1145      +/-   ##
==========================================
+ Coverage   76.72%   76.75%   +0.02%     
==========================================
  Files          87       82       -5     
  Lines        6655     6482     -173     
==========================================
- Hits         5106     4975     -131     
+ Misses       1549     1507      -42     

Impacted Files	Coverage Δ
jdaviz/configs/cubeviz/plugins/viewers.py	95.23% <0.00%> (-2.39%)	⬇️
jdaviz/core/tools.py	74.57% <0.00%> (-1.47%)	⬇️
jdaviz/app.py	88.95% <0.00%> (-1.03%)	⬇️
jdaviz/configs/specviz/plugins/viewers.py	64.91% <0.00%> (-0.29%)	⬇️
jdaviz/configs/imviz/plugins/viewers.py	82.73% <0.00%> (-0.25%)	⬇️
jdaviz/configs/default/plugins/__init__.py	100.00% <0.00%> (ø)
...iz/configs/default/plugins/export_plot/__init__.py
...nfigs/default/plugins/plot_options/plot_options.py
...configs/default/plugins/export_plot/export_plot.py
jdaviz/components/toolbar_nested.py
... and 8 more

---

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 b2e6c8d...e0f639f. Read the comment docs.

[dhomeier]

Why is this not working for that one job? 🤔

I had the same problems in glue-viz/glue-jupyter#297 – looks like the warnings filter does not help if it raises already in the collection step.

[pllim]

Yeah, @dhomeier . It is already fixed in glue dev, so it will go away with the next glue release.

[dhomeier]

Yes, I've seen it, just had not found the right devdeps environment in glue-jupyter to test against that.

[pllim]

I need this in and I haven't heard objection, so #yolo.