resource leaks in HTTP server and Prisma client shutdown

[EkberHasanov]

Have a Keystone on kubernetes as a pod with database connections.
Up the pod and in docker image run npm cms:start which is in package.json scripts/
Send multiple requests to the server
Then delete the pod. I have frontend, nodered and etc.. and I can successfully implement gracefulShutdown function ot them so that they can close DB connections before getting deleted.

When shutting down, Keystone should:
Call server.close() on the HTTP server to allow existing connections to complete
Call prisma.$disconnect() to cleanly shut down the Prisma client
Exit only after all resources are properly closed

I think this info would be irrelevant, but anyway: Dockerfile: FROM node:22-slim.

[EkberHasanov]

I already drafted small code solution for this one, perhaps I can do PR so you can review:

packages/core/src/lib/createSystem.ts

    getKeystone: (PM: any) => {
      const prePrismaClient = new PM.PrismaClient({
        datasourceUrl: formatUrl(config.db.provider, config.db.url),
        log: config.db.enableLogging,
      })

      const prismaClient = config.db.extendPrismaClient(injectNewDefaults(prePrismaClient, lists))
      const context = createContext({
        config,
        lists,
        graphQLSchema,
        graphQLSchemaSudo,
        prismaClient,
        prismaTypes: {
          DbNull: PM.Prisma.DbNull,
          JsonNull: PM.Prisma.JsonNull,
        },
      })

      return {
        async connect() {
          await (prismaClient as any).$connect()
          await config.db.onConnect?.(context)
        },
        
        async disconnect() {
          try {
            await (prismaClient as any).$disconnect()
          } catch (err) {
            console.error('Error while disconnecting from the database:', err)
          }
        },
        
        context,
      }
    },

[EkberHasanov]

Or maybe you might consider having keystone stop command in order to shut down keystone server properly