MNT: glue-jupyter compatibility for import

[pllim]

Description

Blocked by:

• TST: Pick up astropy-dev from index URL to get latest dev wheel #2358

MNT: glue-jupyter compatibility for import for glue-viz/glue-jupyter#379 . If we end up needing to bump minversion of glue-jupyter to 0.18 anyway for other reasons, then we do not need the compatibility layer and can just switch straight to new import.

TST: Temporarily ignore DeprecationWarning from astropy/numpy dev that is already fixed in astropy/astropy#15116 . This should go away on its own when astropy uploads new dev wheel and then we can remove the ignore added here. I just need this out of the way to see if we get all the glue-jupyter stuff.

TST: Use legacy numpy print option so we don't have to deal with the new print, yet.

Change log entry

• Is a change log needed? If yes, is it added to CHANGES.rst? If you want to avoid merge conflicts,
  list the proposed change log here for review and add to CHANGES.rst before merge. If no, maintainer
  should add a no-changelog-entry-needed label.

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 milestone set? Set this to bugfix milestone if this is a bug fix and needs to be released ASAP; otherwise, set this to the next major release milestone.
• After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@4bcc1b1). Click here to learn what that means.
Patch coverage: 80.00% of modified lines in pull request are covered.

❗ Current head 25d5738 differs from pull request most recent head 2956f06. Consider uploading reports for the commit 2956f06 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2336   +/-   ##
=======================================
  Coverage        ?   90.53%           
=======================================
  Files           ?      152           
  Lines           ?    17370           
  Branches        ?        0           
=======================================
  Hits            ?    15726           
  Misses          ?     1644           
  Partials        ?        0           

Files Changed	Coverage Δ
...nfigs/default/plugins/plot_options/plot_options.py	93.35% <75.00%> (ø)
jdaviz/configs/default/plugins/viewers.py	96.47% <75.00%> (ø)
jdaviz/core/astrowidgets_api.py	97.18% <80.00%> (ø)
jdaviz/utils.py	88.88% <100.00%> (ø)

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

[pllim]

Should be uncontroversial. Nothing we can do about this anyway. Friday night YOLO!