[house] Add a Jinja test template

[IsaacG]

This changes the expecations for the output layout.
This brings the exercise in line with the problem spec and breaks all existing solutions.

[github-actions]

This PR touches files which potentially affect the outcome of the tests of an exercise. This will cause all students' solutions to affected exercises to be re-tested.

If this PR does not affect the result of the test (or, for example, adds an edge case that is not worth rerunning all tests for), please add the following to the merge-commit message which will stops student's tests from re-running. Please copy-paste to avoid typos.

[no important files changed]

For more information, refer to the documentation. If you are unsure whether to add the message or not, please ping @exercism/maintainers-admin in a comment. Thank you!

[IsaacG]

+cc @exercism/bash This changes the expected output format to match the problem spec, breaking existing implementations. Thoughts on changing this exercise in that way? Any objections?

Personally, I think moving things towards the problem spec is generally good.

[kotp]

I am for it, and the output change is likely an easy change for the solutions that exist. We could still commit with the "[no important files changed]" if we want to have students to opt-in on the changes, without invalidating their solutions, right?

[glennj]

Does anyone remember why we started putting version numbers into the tests? This change is going backwards.

[IsaacG]

I have no idea why we do those. I'm in favor of dropping them.

Do you have preferences on adding the test UUIDs for each test (could be done at the same time)?

[glennj]

We don't currently have a reason to include the UUIDs. Unless we want to use them to disambiguate tests with the same name in different test groups.

[IsaacG]

Done