fix(core): isolate nested transient providers in static context

[mag123c]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior?

When multiple DEFAULT scoped providers inject the same TRANSIENT → TRANSIENT chain, the nested TRANSIENT instances are incorrectly shared

• DefaultParent1 → TransientService[1] → NestedTransient[1]
• DefaultParent2 → TransientService[2] → NestedTransient[1] ← Shared!

This is because getEffectiveInquirer() has a contextId !== STATIC_CONTEXT condition that excludes STATIC context from nested TRANSIENT isolation logic.

Issue Number: #16257

What is the new behavior?

Each DEFAULT scoped parent now receives its own isolated nested TRANSIENT chain

• DefaultParent1 → TransientService[1] → NestedTransient[1]
• DefaultParent2 → TransientService[2] → NestedTransient[2] ← Isolated!

Does this PR introduce a breaking change?

• Yes
• No

Other information

cc. @Legiew

[coveralls]

Pull Request Test Coverage Report for Build adaf2e50-9fbb-4438-b086-14d3e112471e

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.01%) to 89.743%

---

Files with Coverage Reduction	New Missed Lines	%
packages/core/injector/instance-wrapper.ts	1	95.53%

Totals
Change from base Build d3739886-8f7f-46b1-9469-82eecbaff18b:	-0.01%
Covered Lines:	7446
Relevant Lines:	8297

---

💛 - Coveralls