Add duration to mongo logging

[garrensmith]

Bug description

With this code

 const prisma = newPrismaClient({
        log: [
          {
            emit: 'event',
            level: 'info',
          },
          {
            emit: 'event',
            level: 'query',
          },
        ],
      })
prisma.$on('query', onQuery)
 await prisma.user.findMany()

when using mongo I get following event:

{
      is_query: true,
      item_type: 'query',
      level: 'debug',
      module_path: 'mongodb_query_connector::query',
      params: '[]',
      query: 'db.User.aggregate([ { $project: { _id: 1, }, }, ])'
}

where with sqlite or any other provider I get someting along these lines:

{
      duration_ms: 0,
      is_query: true,
      item_type: 'query',
      level: 'debug',
      module_path: 'quaint::connector::metrics',
      params: '[-1,0]',
      query: 'SELECT `main`.`User`.`id` FROM `main`.`User` WHERE 1=1 LIMIT ? OFFSET ?',
      result: 'success'
}

How to reproduce

Expected behavior

MongoDB logs should include the duration in the log event.

Prisma information

Environment & setup

• OS:
• Database:
• Node.js version:

Prisma Version

[Jolg42]

Should we add a test in prisma/prisma about MongoDB logs? I'm not sure if we have one.

[miguelff]

Some are being added to prisma in #15957

On the engine side, we have a couple of integration tests covering that logs are indeed being generated and that fields contain both a duration and a query string. Then we have a complete unit test suite for the log traces' query strings. I'm in favor of adding more tests that contribute to the client's robustness, but I will defer to @danstarns on the decision of which and how many of them would constitute good enough coverage.

[danstarns]

Coverage added in this PR & commit: 65cdef6