Guard calling after_transition when exception encountered

[zangell44]

This PR adds logic to guard against calling after_transition if orchestration encountered an error.

This applies in cases where, for example, we could encountered in error trying to secure concurrency slots in before_transition because of a connectivity issue with the database. Often exceptions of this sort will impact our ability to communicate with the database further, resulting in mishandled errors.

Closes https://github.com/PrefectHQ/nebula/issues/1041

Example

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• This pull request includes tests or only affects documentation.
• This pull request includes a label categorizing the change e.g. fix, feature, enhancement

[netlify]

✅ Deploy Preview for prefect-orion ready!

Name	Link
🔨 Latest commit	ef9d62f
🔍 Latest deploy log	https://app.netlify.com/sites/prefect-orion/deploys/634969d505cbad000856f2c9
😎 Deploy Preview	https://deploy-preview-7156--prefect-orion.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[zanieb]

I thought this was intentional to ensure that after_transition could be used to clean up side-effects on failure? cc @anticorrelator

I have been informed that this is not the case :)

Gosh "errorred" is ugly to read though. Can we just do "transition_error" or "transition_exception" or "exception_in_transition"?

[zanieb]

LGTM