feat(ui): add action to explorer item to show the test/suite line in the source code tab

[userquin]

Description

Closes #5931

This PR includes:

• new action in the explorer item to go to the test/suite line in the source code tab: will navigate to the tab if the ViewEditor is not the code tab or the active file is not the selected
• enable includeTaskLocation if running in browser mode (not headless) or ui mode: will preserve user option - @sheremet-va review config.ts module 🙏
• docs: update config/index.md to include previous entry
• when the user disables includeTaskLocation, the explorer item will show a tooltip similar for coverage without html reporter (check image below): we can just disable the button...
• refactor codemirror logic: moved codemirrror shallow ref from the ViewEditor to a global shallow ref inside codemirror composable, removed exposed codemirror from the ViewEditor and updated all usages with the global one
• added navigateTo to navigator.ts composable to allow change the view mode: navigator sfc and explorer item using it, without view mode and with it respectively
• added disabled run test/suite for future usage: we'll need to change the logic to allow run individual tests/suites.

You can see this PR in action in this video.

Disabled includeTaskLocation

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[userquin]

When running test/core with Vitest UI I get this error that should be fixed (or maybe not):

[userquin]

Added code tab and source files to the gz file when running pnpm vitest --reporter=html: last commit also enables includeTaskLocation when using html reporter.

NOTE: codemirror in readOnly mode when running vitest with --reporter=html and so we can copy/paste enabling focusing and scrolling from explorer item sfc

[userquin]

Dont merge yet, I'll change the explorer ítem ui again (missing tooltip when html reporter).

[wll8]

@userquin Is codemirrorRef guaranteed to be initialized after 256 milliseconds?

// we need to await, CodeMirrow will take some time to initialize
await new Promise(r => setTimeout(r, 256))

packages/ui/client/composables/codemirror.ts

[userquin]

It is about waiting for route change and 100ms in the onMounted, maybe I can try using another approach to load it.

[userquin]

[userquin]

@userquin Is codemirrorRef guaranteed to be initialized after 256 milliseconds?

// we need to await, CodeMirrow will take some time to initialize
await new Promise(r => setTimeout(r, 256))

packages/ui/client/composables/codemirror.ts

Now the logic will focus the line based on the new line router param, forcing the new watcher to trigger in ViewEditor once the new code loaded

[maxpatiiuk]

added disabled run test/suite for future usage: we'll need to change the logic to allow run individual tests/suites.

Sorry if I am late, but could you please clarify why the ability to run individual test was disabled?

Is is something that is coming in the future? Is there a feature request for that or should I open one?

Thanks!

[sheremet-va]

This was never supported. It is possible to support - feel free to create an issue or a PR