Fixed graceful disposal on SIGTERM shutdown in message processors

[Bazze]

I discovered something that I think is a bug (?). The processor's shutdown handler was calling close({}) instead of close(startOptions), losing the connection context. This caused postgreSQLProcessingScope to throw "missing connection string" when a processor was terminated via SIGTERM.

I had below error when my local docker container restarted on file changes.

[...]/node_modules/@event-driven-io/emmett-postgresql/src/eventStore/consumers/postgreSQLProcessor.ts:238
      throw new EmmettError(
            ^
_EmmettError: PostgreSQL processor 'reactor:tenant-bootstrap' is missing connection string. Ensure that you passed it through options
    at processingScope ([..]/node_modules/@event-driven-io/emmett-postgresql/src/eventStore/consumers/postgreSQLProcessor.ts:238:13)
    at close ([...]/node_modules/@event-driven-io/emmett/src/processors/processors.ts:416:13)
    at process.<anonymous> (/[...]/node_modules/@event-driven-io/emmett/src/processors/processors.ts:435:38)
    at process.emit (node:events:520:35)
    at process.emit (/app/node_modules/tsx/dist/suppress-warnings.cjs:1:472) {
  errorCode: 500
}

[oskardudycz]

@Bazze, I think there's something odd happening in the PostgreSQL processor as well. The processor shouldn't require those options; it should just clean up what it has active. As this is fixing the issue for now, I'm going to merge it and later try to improve it. Thanks a lot for doing that. 👍