fix(cursor): throw error in ChangeStream constructor if changeStreamThunk() throws a sync error

[vkarpov15]

Summary

An unintended consequence of #14813 using promises rather than event emitters is that sync errors in changeStreamThunk() aren't possible to handle. Model.watch().on('error') doesn't work because the constructor throws an error before the on('error') call happens.

This PR makes ChangeStream() constructor throw an error if changeStreamThunk() throws a synchronous error. The code is a little clunky, but at least avoids silently ignoring sync errors in changeStreamThunk(). This code is hard to test because changeStreamThunk() doesn't throw in Mongoose in general.

Examples

[hasezoey]

Code looks good to me.

Though some of the replica-set runs (both push & pull_request) had failed with: (which i assume has nothing todo with this PR in particular)

   1) transactions
       distinct (gh-8006):
     MongoServerError: Given transaction number 4 does not match any in-progress transactions. The active transaction number is 3
      at Connection.sendCommand (node_modules/mongodb/lib/cmap/connection.js:290:27)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async Connection.command (node_modules/mongodb/lib/cmap/connection.js:313:26)
      at async Server.command (node_modules/mongodb/lib/sdam/server.js:167:29)
      at async InsertOneOperation.executeCommand (node_modules/mongodb/lib/operations/command.js:73:16)
      at async InsertOneOperation.execute (node_modules/mongodb/lib/operations/insert.js:37:16)
      at async InsertOneOperation.execute (node_modules/mongodb/lib/operations/insert.js:46:21)
      at async executeOperation (node_modules/mongodb/lib/operations/execute_operation.js:136:16)
      at async Collection.insertOne (node_modules/mongodb/lib/collection.js:154:16)

[vkarpov15]

@hasezoey correct, looks like a flakey test