Adds documentation to specify HOVER version and known GLIBCXX error (#588)

# Description

- Adds a note in the HOVER doc to indicate support for Isaac Lab 2.0 and
Isaac Sim 4.5, as there are several issues with running it on Isaac Lab
2.2
- Adds a section in the Known Issues to highlight GLIBCXX error we have
observed in conda environments and provides a workaround for resolving
the error


## Type of change

- This change requires a documentation update


## Checklist

- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./isaaclab.sh --format`
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have updated the changelog and the corresponding version in the
extension's `config/extension.toml` file
- [ ] I have added my name to the `CONTRIBUTORS.md` or my name already
exists there

<!--
As you go through the checklist above, you can mark something as done by
putting an x character in it

For example,
- [x] I have done this task
- [ ] I have not done this task
-->

docs/source/policy_deployment/00_hover/hover_policy.rst

@@ -17,6 +17,9 @@ Installation
 
    This tutorial is for linux only.
 
+   HOVER supports Isaac Lab 2.0 and Isaac Sim 4.5. Please ensure you have the correct version of Isaac Lab and Isaac Sim installed to run the HOVER workflow.
+
+
 1. Install Isaac Lab following the instructions in the `Isaac Lab Installation Guide`_.
 
 2. Define the following environment variable to specify the path to your Isaac Lab installation:

docs/source/refs/issues.rst

@@ -91,3 +91,13 @@ This is due to the termination occurring in the middle of a physics event call a
 should not affect the functionality of Isaac Lab. It is safe to ignore the error
 message and continue with terminating the process. On Windows systems, please use
 ``Ctrl+Break`` or ``Ctrl+fn+B`` to terminate the process.
+
+
+GLIBCXX errors in Conda
+-----------------------
+
+In Isaac Sim 5.0, we have observed some workflows exiting with an ``OSError`` indicating
+``version 'GLIBCXX_3.4.30' not found`` when running from a conda environment.
+The issue apperas to be stemming from importing torch or torch-related packages, such as tensorboard,
+prior to launching ``AppLauncher``. As a workaround, ensure that all torch imports happen after
+the ``AppLauncher`` instance has been created, which should resolve the error.