Use lcviz version in all docs links

[kecnry]

This PR ensures that all internal docs links buttons point to the correct version on RTD, and don't use the upstream version tag set by jdaviz.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.21%. Comparing base (7b78df5) to head (acbab50).
Report is 35 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #128      +/-   ##
==========================================
- Coverage   93.92%   91.21%   -2.72%     
==========================================
  Files          37       41       +4     
  Lines        1598     2082     +484     
==========================================
+ Hits         1501     1899     +398     
- Misses         97      183      +86     

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

[kecnry]

to test, override this with 'v0.4.1' and see that all links in plugins and the app toolbar point correctly to that tagged release on RTD.

[bmorris3]

Is this only necessary for RTD? If so, can it be solved with the same approach as spacetelescope/jdaviz#3080?

[kecnry]

this is links from the app to RTD (like the button in the app-toolbar and "learn more" links in each plugin - so no).

[bmorris3]

This works for me locally. I regret that any of this needs to be accomplished by observing a traitlet, but it's not clear how to avoid that without something much more complicated.

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

git checkout v0.4.x
git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

git cherry-pick -x -m1 3853abe51f719805f379b8b5015fd5bbd53e0088

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

git commit -am 'Backport PR #128: Use lcviz version in all docs links'

4. Push to a named branch:

git push YOURFORK v0.4.x:auto-backport-of-pr-128-on-v0.4.x

5. Create a PR against branch v0.4.x, I would have named this PR:

"Backport PR #128 on branch v0.4.x (Use lcviz version in all docs links)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.