fix: potential stack overflow when computing types of lambda parameters

[lars-reimann]

Summary of Changes

Due to the interaction between the type computer and the scope provider, the previous approach to prevent endless recursion when computing the type of lambda parameters could fail. This PR provides a more robust implementation to fix this issue.

[github-actions[bot]]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ REPOSITORY	git_diff	yes		no	0.14s
✅ TYPESCRIPT	eslint	1	0	0	4.46s
✅ TYPESCRIPT	prettier	1	0	0	1.13s

See detailed report in MegaLinter reports _Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff_

_MegaLinter is graciously provided by _

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (a07e893) to head (af619cd).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1173 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 110 110 Lines 19238 19227 -11 Branches 4114 4119 +5 ========================================= - Hits 19238 19227 -11 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[lars-reimann]

:tada: This PR is included in version 0.16.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• v0.16.0
• GitHub release

Your semantic-release bot :package::rocket: