[Resolve #1519] PoC for centralised exception handling

[alex-harvey-z3q]

Proof of concept for centralised exception handling.

See also https://github.com/Sceptre/sceptre/pull/1522

PR Checklist

• [ ] Wrote a good commit message & description [see guide below].
• [x] Commit message starts with [Resolve #issue-number].
• [ ] Added/Updated unit tests.
• [ ] Added/Updated integration tests (if applicable).
• [x] All unit tests (poetry run tox) are passing.
• [x] Used the same coding conventions as the rest of the project.
• [x] The new code passes pre-commit validations (poetry run pre-commit run --all-files).
• [x] The PR relates to only one subject with a clear title. and description in grammatically correct, complete sentences.

Approver/Reviewer Checklist

• [ ] Before merge squash related commits.

Other Information

Guide to writing a good commit

[alex-harvey-z3q]

I think handling in connection manager seems like the right place therefore i think i prefer this over PR #1522. However instead of using this approach how about we switch to a cleaner approach using aws-error-utils which i found here https://stackoverflow.com/a/33663484

I am not sure I like that idea, as it introduces a dependency on a third party project and, by the looks of it, has not been committed to in over a year https://github.com/benkehoe/aws-error-utils

I agree with you that handling all of these exceptions is going to lead to some bloat and we may eventually need another helper method but I think we'll figure it out and keep the code clean?

[alex-harvey-z3q]

What do you think @dboitnot ?