Add automations to prefect.yaml for deployments

[sra-mitch]

First check

• [X] I added a descriptive title to this issue.
• [X] I used the GitHub search to find a similar request and didn't find it.
• [X] I searched the Prefect documentation for this feature.

Prefect Version

2.x

Describe the current behavior

Currently, automations on prefect cloud are only able to be set using the UI. It is time consuming and difficult to view all of the automations on the prefect cloud UI.

Describe the proposed behavior

Prefect automations will be able to be deployed via the prefect.yaml file for each of the deployments in the file. A user would have the same options which are visible on the UI, or be able to add a deployment to an existing automation (think a generic retry automation).

Example Use

A user would create a depoyment within their prefect.yaml

   - name: Test-Deployment
      description: null
      entrypoint: test.py:test_func
      work_pool: *default_work_pool
      parameters: {
       }
      schedule:
          cron: 2 9 * * 1-5
          timezone: "America/Chicago" 
         automations:
          trigger: Flow run state
          state: ['Failed' , 'Crashed', 'TimedOut']
          action:
               notification:
                    block: test-slack-webhook

Additional context

No response

[WillRaphaelson]

Thanks @sra-mitch, I'll add this to the backlog. As we already support triggers on the deployment object, which dictate when an event driven flow should run by bootstrapping an automation under the hood, we could consider a few different interfaces for this.

• Move triggers into an overarching automations key (in a backwards compatible way) that would support both triggering automations and automations to execute on specific state changes.
• Have both triggers and state_automations or down_stream_automations or something like that