Remove warnings in docs

[echedey-ls]

• [ ] Closes #xxxx
• I am familiar with the contributing guidelines
• [ ] Tests added
• [ ] Updates entries in docs/sphinx/source/reference for API changes.
• [ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
• [ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
• Pull request is nearly complete and ready for detailed review.
• Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

I forgot to check the built docs log ☠️
Second commit has the log output of that equation problem

• Fixes

  • Broken hyperlinks
  • Warning of duplicated equation label
  • Version switcher position text, with Bump docs infraestructure #2112 it's position got changed. Credit of @RDaxini for spotting it

[echedey-ls]

@IoannisSifnaios @RDaxini this documentation log is almost clean. Double-checking exercise left to the reader 🙃

[RDaxini]

LGTM, I can see that the links are working now and you've removed the additional label.

Possible additional revision while we're at it though... in the Plot Irradiance Non-uniformity Loss example, can we separate the first code block (the one importing packages) more distinctly from the references section? I just think it would look neater. I know anyone would know that's not references, but it kinda looks like it is part of that section. Perhaps shift it into the problem description section? It could still be kept as a separate code block from the code block already in that section though. Just an idea.

[echedey-ls]

can we separate the first code block (the one importing packages)

You've got a point right there @RDaxini , thx!

[kandersolar]

LGTM, thanks @echedey-ls!