SERVER-132721Backlog

Require LiteParserOptions in all nested-pipeline lite-parsed stage constructors

The problem is that a stage can end up with a null context, and we may make the wrong decision based on this missing context wrt ifr flag features.  It was the root cause of the {{$lookup}} failure investigated under SERVER-132516: {{LiteParsedLookUp::getIfrContext()}} was always null because {{{}LiteParsedLookUp{}}}'s constructor used the no-options single-pipeline overload. Fixed there by adding an options-taking variant and threading {{options}} through, but only for {{{}$lookup{}}}. h

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification
dino-extensions-apidino-tech-debt