Strictly typed Query Cursor async iterator

[borfig]

Do you want to request a feature or report a bug?
IMHO, it is a feature.

What is the current behavior?
When using for await with query cursors, the returned objects are of type any, which can hide possible bugs.

The following buggy TypeScript code compiles, and the bug will be discovered only in runtime:

import { Schema, model } from "mongoose";
interface Test {
  test: string;
}
const schema = new Schema<Test>({
  test: { type: String, required: true },
});
const TestModel = model<Test>("Test", schema);
async function main() {
  const cursor = TestModel.find({}).cursor();
  for await (const test of cursor) {
    console.log(test.tedt); // intentional bug
  }
}
main()

My tsconfig.json:

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es2019",
    "lib": [
      "dom",
      "es2019",
      "es2020.bigint",
      "es2020.string",
      "es2020.symbol.wellknown",
    ],
    "esModuleInterop": true,
    "strict": true,
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "sourceMap": true,
    "outDir": "dist",
    "baseUrl": ".",
    "jsx": "react"
  },
  "include": [
    "src/**/*.ts*",
  ]
}

What is the expected behavior?
I am proposing to change the QueryCursor's [Symbol.asyncIterator] to return a strictly-typed AsyncIterableIterator<DocType>, instead of the inherited AsyncIterableIterator<any>

What are the versions of Node.js, Mongoose and MongoDB you are using? Note that "latest" is not a version.

• Mongoose v5.12.9
• Node.js v12.22.1
• MongoDB v4.4.6
• TypeScript v4.2.4