Support for NotificationChannel in Textract Caller's Async Methods

[azucker99]

The standard paradigm for using Textract's asynchronous API to process multi-page documents is to publish the completion status to an SNS topic for consumption by a downstream consumer (e.g., SQS, Lambda, etc.). Currently, the Textractor method mappings do not support the NotificationChannel parameter required for sending a completion status to an SNS topic:

amazon-textract-textractor/textractor/textractor.py

Lines 425 to 439 in e608576

	response = call_textract(
	input_document=file_source,
	features=features,
	queries_config=queries, # not supported yet
	output_config=None,
	kms_key_id=self.kms_key_id,
	job_tag="",
	notification_channel=None, # not supported yet
	client_request_token="",
	return_job_id=False,
	force_async_api=False,
	call_mode=Textract_Call_Mode.FORCE_SYNC,
	boto3_textract_client=self.textract_client,
	job_done_polling_interval=0,
	)

Adding the option to pass the notification_channel to the Textract asynchronous API method mappings would be beneficial in closing the loop on the asynchronous document processing paradigm.