plugins: disable action button while computing

[kecnry]

Description

This pull request implements re-usable infrastructure via a @with_spinner() method, which sets the spinner traitlet to True at the beginning of a method, and resets to False when it completes (successfully or not). This traitlet can then be used to disable and change the icon on the action button by passing it to <plugin-add-results :action_spinner='spinner'>. For expensive operations, this provides immediate feedback that something is happening and avoids the user clicking the button again before the action completes.

For more advanced cases, individual boolean traitlets can be added to the plugin and controlled separately by passing the name of the traitlet to the decorator. For example @with_spinner('spinner_custom').

All the logic lives in template_mixin.py and plugin_add_results.vue... everything else is just using that within all the various applicable plugins.

Example for model fitting a cube (but this PR applies the logic to all existing plugin-add-results buttons and a few others):

Screen.Recording.2023-11-10.at.2.01.03.PM.mov

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

All modified and coverable lines are covered by tests ✅

Files	Coverage Δ
...configs/cubeviz/plugins/moment_maps/moment_maps.py	92.55% <100.00%> (+0.08%)	⬆️
...plugins/spectral_extraction/spectral_extraction.py	69.07% <100.00%> (+0.32%)	⬆️
...daviz/configs/default/plugins/collapse/collapse.py	98.07% <100.00%> (+0.03%)	⬆️
...configs/default/plugins/export_plot/export_plot.py	60.40% <100.00%> (+1.06%)	⬆️
...default/plugins/gaussian_smooth/gaussian_smooth.py	97.89% <100.00%> (+0.04%)	⬆️
...igs/default/plugins/model_fitting/model_fitting.py	86.59% <100.00%> (+0.02%)	⬆️
...nfigs/default/plugins/plot_options/plot_options.py	91.20% <100.00%> (-0.03%)	⬇️
...imviz/plugins/aper_phot_simple/aper_phot_simple.py	91.13% <100.00%> (+0.03%)	⬆️
jdaviz/configs/imviz/plugins/catalogs/catalogs.py	86.72% <100.00%> (+0.11%)	⬆️
...plugins/spectral_extraction/spectral_extraction.py	90.97% <100.00%> (+0.20%)	⬆️
... and 1 more

📢 Thoughts on this report? Let us know!

[rosteen]

I really like this now with the spinner rather than check marks - code looks fine, approved.