Fix using template parts via render-template

[patrickbkr]

The @*CRO-TEMPLATE-PART-PROVIDERS dynvar was only set in the template multis. Moving it to render-internal should cover all needed code paths.

[japhb]

We've got a compatibility problem in our CI -- it looks like it may be failing to install dependencies on 2021.03, and of course to save compute time GH just cancels all the test jobs when any one fails.

However I reran only ubuntu-latest/latest to work around the incompatibility and that gave:

https://github.com/croservices/cro-webapp/actions/runs/8179001098/job/22368196868

That looks actually related to the content of the PR. @patrickbkr Can you take a look at that one?

[patrickbkr]

I believe render-template should behave the same as template, just as the documentation states.

It's an interesting problem. In the tests render-template is used outside of a route block. router-plugin-get-configs throws when called outside a route or middleware block.

To make render-template (and template as well) usable outside route blocks, I could either make the setting of @*CRO-TEMPLATE-PART-PROVIDERS conditional duplicating the same checks. Or I catch the respective exception and ignore it. Ignoring the exception seems like the more maintainable approach, but uses an exception in a non-error code path. (Which is generally considered bad practice.) I still think that's the best approach. Other ideas?

[patrickbkr]

I went with the CATCH approach. All tests should pass now.