We have multiple methods / identifiers in various top level aggregation processing structures that mark if a query / stage is a rank fusion.

Examples:

• LiteParsedDocumentSource
• LiteParsedPipeline
• AggExState
• ExpressionContext
• DocumentSourceRankFusion
• AggregateCommand IDL

We have these methods to ban certain features that rank fusion cannot support and/or support rank fusion queries on views.

We should generalize these methods to determine if a stage is a hybrid search ($rankFusion or $scoreFusion), as the same top level query behavior should apply to both stages.

For the IDL changes (for communication across mongod & mongos) we may have to have a separate _isRankFusion and _isScoreFusion field to support backwards compatibility between 8.1 and 8.2.

Also, in this effort see if any isRankFusion variables / functions can be deleted instead of generalized