Make handlerOptions optional in RequestHandler

[trivikr]

Is your feature request related to a problem? Please describe.
Not a problem, but an empty hash needs to be passed for httpOptions when calling handle function.

Code links:

• RequestHandler:

  aws-sdk-js-v3/packages/types/src/transfer.ts

  Line 11 in 9e58bbb

  handle: (request: RequestType, handlerOptions: HandlerOptions) => Promise<RequestHandlerOutput<ResponseType>>;

• The keys in HttpHandlerOptions are optional

  aws-sdk-js-v3/packages/types/src/http.ts

  Lines 96 to 101 in 96f61bb

  	/**
  	* Represents the options that may be passed to an Http Handler.
  	*/
  	export interface HttpHandlerOptions {
  	abortSignal?: AbortSignal;
  	}

• node-http-handler

  aws-sdk-js-v3/packages/node-http-handler/src/node-http-handler.ts

  Line 53 in 9e58bbb

  handle(request: HttpRequest, { abortSignal }: HttpHandlerOptions): Promise<{ response: HttpResponse }> {

• node-http2-handler

  aws-sdk-js-v3/packages/node-http-handler/src/node-http2-handler.ts

  Line 43 in 9e58bbb

  handle(request: HttpRequest, { abortSignal }: HttpHandlerOptions): Promise<{ response: HttpResponse }> {

• fetch-http-handler

  aws-sdk-js-v3/packages/fetch-http-handler/src/fetch-http-handler.ts

  Line 28 in 9e58bbb

  handle(request: HttpRequest, options: HttpHandlerOptions): Promise<{ response: HttpResponse }> {

Describe the solution you'd like
Make handlerOptions optional in RequestHandler

Describe alternatives you've considered
Stick with required handlerOptions, as it's used internally by client code and not directly called by customers.

Additional context
This was noticed while writing new unit tests for node-http-handler in #1693

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.