Expose GraphQLModule options and gqlSchemaHost to support Serverless

[amokio]

Is there an existing issue that is already proposing this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe it

No

Describe the solution you'd like

when use createApplicationContext, GraphQLModule it will not run adapter.start() and create ApolloServer because of httpAdapter is null.

to support serverless, can we expose options and gqlSchemaHost.schema so that we can manual create ApolloServer

import { ApolloFederationDriver } from '@nestjs/apollo';
import { NestFactory } from '@nestjs/core';
import { GraphQLModule } from '@nestjs/graphql';
import { AppModule } from './app.module';
import { ApolloServer } from '@apollo/server';
import {
  LambdaHandler,
  handlers,
  startServerAndCreateLambdaHandler,
} from '@as-integrations/aws-lambda';

const requestHandler = handlers.createAPIGatewayProxyEventV2RequestHandler();

let serverless: LambdaHandler<typeof requestHandler>;

const bootstrap = async () => {
  if (!serverless) {
    const app = await NestFactory.createApplicationContext(AppModule, {
      logger: ['error'],
    });

    await app.init();

    const graphql =
      app.get<GraphQLModule<ApolloFederationDriver>>(GraphQLModule);

    const options = (graphql as any).options;

    const server = new ApolloServer({
      ...options,
      schema: (graphql as any).gqlSchemaHost.schema,
    });

    serverless = startServerAndCreateLambdaHandler(server, requestHandler, {});
  }
};

bootstrap();

export const handler = async (event, context, callback) => {
  if (!serverless) {
    await bootstrap();
  }

  return serverless(event, context, callback);
};

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

integrate with @as-integrations/aws-lambda