Allow user-defined TEST_PROTECT & TEST_ABORT macros

[fkjagodzinski]

This update covers use cases where:

• Unity is used to provide the assertion macros only, and an external test harness/runner is used for test orchestration/reporting, e.g. Mbed OS.
• Calling longjmp on a given platform is possible, but has a platform-specific (or implementation-specific) set of prerequisites, e.g. privileged access level. Which has been mentioned in https://github.com/ThrowTheSwitch/Unity/issues/616#issuecomment-1155219717.

Enable project-specific customisation of TEST_PROTECT and TEST_ABORT macros:

• Use the user-defined UNITY_TEST_ABORT if available; fall back to default behaviour otherwise.
• Use the user-defined UNITY_TEST_PROTECT if available; fall back to default behaviour otherwise.
• These may be defined independently.

[fkjagodzinski]

Marking this as a draft because the patch is missing docs update. :slightly_smiling_face:

Also, please let me know if this path is acceptable, then I'll update the relevant markdown files.

[mvandervoord]

Hi. Thanks for the patch! I appreciate that you've matched the pattern of usage we have for other override-able options in the project. If you update the configuration docs with this, I'd say you have a great feature here. :)

[fkjagodzinski]

I've updated the docs. I think the macro descriptions are OK, but my view is rather biased, so I'd appreciate any reviews. :wink:

[fkjagodzinski]

Hi there. It's been a while so I took another look at the docs, and I'd say both the macro descriptions and the code snippets still make sense. @mvandervoord, could you review the PR when you get a chance?