fix(esbuild): update to tsconfck 3.0.1 to fix edge cases when resolving tsconfig.extends

[dominikg]

update to tsconfck@3.0.1

Changes:

• "extends":".." resolves to ../tsconfig.json fixes extends in tsconfig.json should prefer tsconfig.json over package.json #15371
• fix an edge case where a tsconfig read from cache did not have its extends parsed and applied if it was part of another extended config that was processed before.

Example:

tsconfig.base.json
a/tsconfig.json #extends tsconfig.base.json
a/b/tsconfig.json #extends a/tsconfig.json
a/foo.ts
a/b/bar.ts

const a_b_tsconfig = await parse('a/b/bar.ts'); 
// both 3.0.0 and 3.0.1 return correctly extended result from tsconfig.base.json to a/b/config.json, shallow parsing a/tsconfig.json in the process.

const a_tsconfig = await parse('a/foo.ts'); 
// 3.0.0 returns content of a/tsconfig.json without applied values from tsconfig.base.json if it was previously shallow parsed
// 3.0.1 recognizes that a/tsconfig.json has not been extended yet and does it lazily before returning the value

Unfortunately with this change we can no longer use the direct cache access optimization as the extends parsing is done lazily to avoid the performance penalty if the intermediate tsconfig is never used apart from being extended

Description

Additional context

---

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, especially the Pull Request Guidelines.
• 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).
• Update the corresponding documentation if needed.
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.