Fix code lens bug + added some tests

[karrtikr]

For #6303

This is effectively an un-revert of #6755 (reverted in #6780), with testing fixes.

• Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
• Title summarizes what is changing
• Has a news entry file (remember to thank yourself!)
• Appropriate comments and documentation strings in the code
• Has sufficient logging.
• Has telemetry for enhancements.
• Unit tests & system/integration tests are added/updated
• [ ] Test plan is updated as appropriate
• [ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)
• [ ] The wiki is updated with any design decisions/details.

[ericsnowcurrently]

What is different from #6755? Is it only that you are no longer ignoring roots that do not match the current workspace? Why did you remove that part?

(otherwise looks good)

[karrtikr]

What is different from #6755? Is it only that you are no longer ignoring roots that do not match the current workspace? Why did you remove that part?

(otherwise looks good)

@ericsnowcurrently Yes, current workspace path is not related to data root paths at all. Because test root paths can be anything, as you explained. So removed that entire check, where I was only considering data roots which are equal to workspace root.

[ericsnowcurrently]

We should still ensure that the test root is under the workspace folder, even if it isn't equal.

[karrtikr]

@ericsnowcurrently But that seems unrelated to this issue, right? Would prefer to do it separately if that's the case.

Also, even if tests are outside the workspace, why not discover those tests as well?

[ericsnowcurrently]

I've opened #6820 for dealing with the test roots.

[ericsnowcurrently]

LGTM