Executor Callback support

### Body This is a tracking ticket for the email thread [here](https://lists.apache.org/thread/ssb54kvffc4q95h2ch9j95v10kokmwv5) ## Work Remaining: | Executor | Assignee | Status | PR Link | |----------|----------|--------|---------| | Batch | Sebastian Daum @dondaum | DONE | https://github.com/apache/airflow/pull/62984 | | Celery | Sameer Mesiah @SameerMesiah97 | DONE | https://github.com/apache/airflow/pull/63888| | ECS | Shivam Rastogi @shivaam | DONE | https://github.com/apache/airflow/pull/63657 | | Edge | Jeongwoo Do @wjddn279 | DONE | https://github.com/apache/airflow/pull/67679 | | K8S | Kevin Yang | PR | https://github.com/apache/airflow/pull/63454 | | Lambda | Sameer Mesiah @SameerMesiah97 | DONE | https://github.com/apache/airflow/pull/63035 | - [ ] Convert existing Dag Processor callbacks - Claimed by Sebastian Daum @dondaum A note regarding "claimed" work. This got a lot more attention than I expected, I'm going to put the names down for claimed executors in the order the emails came in. Once I see a PR (please tag me) I'll move it from "claimed" to "work in progress" (WIP). In what I believe to be the spirit of the new assignee policy, if I don't see any progress after a week I'm going to open it back up for someone else. I'm not expecting completion in a week, but I do need to see that you are actively working on it even if it is just asking me questions on Slack. State flow: AVAILABLE -> CLAIMED -> WIP -> PR -> DONE ___ Below the line is just copypasta of the email, for posterity ___ Airflow 3.2 introduces ExecutorCallbacks, allowing executors to run synchronous callbacks (starting with Deadline Alerts). LocalExecutor and CeleryExecutor support is done and tested and I'm looking for volunteers to help implement the remaining executors. There's also an opportunity to help migrate Airflow's existing DAG/task callbacks o…