Enable Destroy Job for Failed First-Time Apply Jobs

When the destroy job is in the "cleanup" stage by default - the entire stage is skipped when the first-time apply job fails.

It does not seem to matter how the job is configured in regard to when: manual rules, it stays in a skipped status.

By moving it to the "deploy" stage, "when: manual" allows the job to be enabled so it can be used when the apply fails the first time around.

In my case of using EKS blueprints - there is a lot of manual cleanup to be done when working through getting a large terraform template migrated to this component.

CC: @timofurrer