Currently `nss` field is propagated to PQS lookup methods, because we want to avoid eagerly compute QueryShape, just to check the nss field of the shape and decide if we should compute QueryShapeHash or early exit.

During implementation of SERVER-84725 we tried to retrieve the `nss` from the `ExpressionContext` that contains the `NamespaceString` information, however, the ExpCtx contains the namespace after view resolution. Which means that we can not distinguish between a query over timeseries view and query over underlying timeseries collection.

When issuing a query over a timeseries collection (system.buckets.*) the query shape hash stability test failed, so we decided to pass nss and be on the safe side.

Once the timeseries dual tracking will be eliminated we can remove passing the nss field to PQS lookup