Instructions to install with anaconda navigator

[camipacifici]

Description

This pull request is to address the lack of instructions to install jdaviz with anaconda navigator.

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. Bugfix milestone also needs an accompanying backport label.
• After merge, any internal documentations need updating (e.g., JIRA, Innerspace)?

[pllim]

Thanks! The rendered doc is at https://jdaviz--3428.org.readthedocs.build/en/3428/installation.html

I am not familiar with Navigator. Do we have to provide additional info to steer them away from the default channel (license drama, outdated versions)?

[pllim]

I think putting conda in the title here is a little misleading because this section covers installation in general, conda or not.

[camipacifici]

Good point. I'll revert this. Thanks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.53%. Comparing base (c72d6f2) to head (e38b8ed).
Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3428   +/-   ##
=======================================
  Coverage   87.53%   87.53%           
=======================================
  Files         128      128           
  Lines       19957    19962    +5     
=======================================
+ Hits        17469    17474    +5     
  Misses       2488     2488           

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

[camipacifici]

I am not familiar with Navigator. Do we have to provide additional info to steer them away from the default channel (license drama, outdated versions)?

I am not sure either. As far as I understand, conda-forge is the first channel and default is the second so it should use conda-forge whenever possible. I do not know if there are other implications.

[pllim]

Thanks for the clear instructions with screenshots!

I double checked with conda build expert. Indeed, it is not possible to ask conda recipe to pip install, so our dependencies and their dependencies need to be all on conda-forge for jdaviz to be useful on conda-forge. FYI.

[camipacifici]

Thank you for checking!