fix: prefer nested config profiles for shared tests

[bennycode]

Summary

• wait until all Vitest configs resolve, then register nested configs first
• keep every matching config tag on shared test files
• order nested profile labels ahead of parent profiles because VS Code sorts defaults by label
• add focused unit and E2E coverage for Vitest extension doesn't run test files with tags #799

Fixes #799