Add async support for Amazon SQS Notifier

[ferruzzi]

Adds async support to the existing SQS Notifier so it can be used as an AsyncCallback for DeadlineAlerts, among other things

dags used for manual testing:

from datetime import datetime, timedelta

from airflow.providers.amazon.aws.hooks.sqs import SqsHook
from airflow.providers.amazon.aws.notifications.sqs import SqsNotifier
from airflow.sdk import task, DAG
from airflow.sdk.definitions.deadline import DeadlineAlert, DeadlineReference, AsyncCallback

PAST_DATE = datetime(1980, 8, 10, 2)
MSG_PREFIX = "SQS Testing Rnd 0:"

DEFAULTS = {"queue_url": "https://sqs.us-east-1.amazonaws.com/324969868898/async-notifier-testing"}


def _sqs_callback(context):
    SqsHook().send_message(**DEFAULTS, message_body=f"{MSG_PREFIX} Hook as Callback -- {context['dag_run'].dag_id}")


@task
def send_sqs_message(message):
    SqsHook().send_message(**DEFAULTS, message_body=message)


@task.bash(task_id='sleep_task')
def sleep_n_secs(seconds):
    return f'sleep {seconds}'


with DAG(
    "sqs_hook_via_taskflow",
    tags=["sqs"]
):
    send_sqs_message(message=f"{MSG_PREFIX} Taskflow -- {{{{ dag_run.dag_id }}}} ")

with DAG(
    "sqs_callback_on_success",
    on_success_callback=_sqs_callback,
    tags=["sqs"],
):
    sleep_n_secs(1)

with DAG(
    "sqs_notifier_as_callback",
    on_success_callback=SqsNotifier(**DEFAULTS, message_body=f"{MSG_PREFIX} Sync Notifier as callback -- {{{{ dag_run.dag_id }}}} "),
    tags=["sqs"],
):
    sleep_n_secs(1)


with DAG(
    "sqs_notifier_as_deadline",
    deadline=DeadlineAlert(
        reference=DeadlineReference.FIXED_DATETIME(PAST_DATE),
        interval=timedelta(0),
        callback=AsyncCallback(
            SqsNotifier,
            kwargs={**DEFAULTS, "message_body": f"{MSG_PREFIX} Async Notifier as Deadline -- {{{{ dag_run.dag_id }}}} "}
        ),
    ),
    tags=["sqs"],
):
    sleep_n_secs(1)

and proof of delivery with intact templating:

cc @ramitkataria @seanghaeli

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.