(REF) WorkflowMessageTest - Use dataProvider

[totten]

Overview

This refactors a unit-test to improve DX.

Before

• testRenderExamples() does a lookup to find examples -- and then loops through and renders each.
• If any of the examples have an exception/error/failure, then the entire test fails - and it's unclear which example raised the problem.

After

• testRenderExamples(string $name) will render an example (based on the name of the example)
• The data-provider getRenderExamples() gives a list.
• PHPUnit reports each test-run as a separate output, so it is easier to match the exception/error/failure to the relevant data.

Technical Details

• The patch looks bigger than it should because of an indentation change (the top loop in testRenderExamples() was removed, so code moved back slightly.)
• In PHPUnit, data-providers are liable to run before Civi has booted. To improve reliability, I switched from the higher-level Civi\Api4\ExampleData to the lower-level Civi\Test::examples()

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[eileenmcnaughton]

ok cool - so to add in any WorkFlowTemplate we just need to add the tag - which we can do once we've worked through the various bits & pieces for them