Reduce stack utilization of TestTemplateTestDescriptor::execute

[amaembo]

Overview

Fixes issue #4020

---

I hereby agree to the terms of the JUnit Contributor License Agreement.

---

Definition of Done

• There are no TODOs left in the code
• Method preconditions are checked and documented in the method's Javadoc -- no method declarations changed
• Coding conventions (e.g. for logging) have been followed
• Change is covered by automated tests including corner cases, errors, and exception handling -- refactoring only change, I believe no new tests are necessary
• Public API has Javadoc and @API annotations -- no public APIs changed
• Change is documented in the User Guide and Release Notes -- should I write something there, or the change is minor and doesn't worth mentioning?

[amaembo]

Not sure about formatting. I've formatted the changed fragment using spotlessApply, even though it's inside the formatter:off section. Probably it worth removing formatter:off.

[jbduncan]

Not sure about formatting. I've formatted the changed fragment using spotlessApply, even though it's inside the formatter:off section. Probably it worth removing formatter:off.

I think so too. From what I've observed of Spotless over the years, users like JUnit 5 use formatter:(off|on) because the bundled Eclipse formatter can't handle fluent chains like streams very well, so the comments are used as an escape hatch. Thus they should be safe to remove, if the team is happy of course. :)

[marcphilipp]

Agreed, let's remove them

[marcphilipp]

@amaembo Thank you for your contribution! I polished it a bit in c29dbb2.