feat(perf): tsconfck perf improvement

[dominikg]

Description

tsconfck 1.1.0 always traverses the parent directories for each code file to find the closest tsconfig.json, needlessly calling fs.stat multiple times.
Initial report here: #7023

tsconfck 1.2.0 gained new options to avoid this by providing a pre-composed list of tsconfig paths that is used instead of the actual filesystem.

This is a potentially breaking change because to be able to provide a complete list of tsconfig files, a root directory has to be set. This PR uses the detected workspace root which should cover most real project setups.

But still it is possible that someone somewhere uses a tsconfig.json outside their workspace root and they will see an error after this is merged

Additional context

for performance reasons, tsconfig.json files are not searched in node_modules or .git directories. Again this could be breaking if someone had something like src/node_modules/tsconfig.json or somehow used ts files and an acccompanying tsconfig directly from an npm package.

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.