ionic/troubleshooting: Document the issue when conda env is at the same directory level as src dir

[peci1]

🦟 Bug fix

Summary

I've lost 4 hours on this...

Checklist

• Signed all commits for DCO
• Added tests
• Updated documentation (as needed)
• Updated migration guide (as needed)
• Consider updating Python bindings (if the library has them)
• codecheck passed (See contributing)
• All tests passed (See test coverage)
• While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

[peci1]

The underlying cause seems to be that colcon tries to traverse everything in the folder it is called in, not only in src. As it finds the conda env dir, it applies colcon_python_setup_py to all python packages installed in the env, and it shows that many packages have wrong setup.py's on conda-forge (e.g. adodbapi (part of pywin32) raises ArrayIndexOutOfBounds, or numpy doesn't distribute numpy.distutils submodule on conda, but it is required in its setup.py).

I'm not sure if this is expected behavior of colcon or a bug.

[azeey]

Oof, what a gnarly problem to face! Thanks for the tip.