Refactor of template files

[jteijema]

This PR:

• Adds a base class for templates and moves duplicate code to the base class
• passes wordcloud flag to docs renderer
• adds allow overwrite flag
• adds a catch for using the wrong template with the wrong template class
• cleans up name passing (name is now only in the template class, or the actual template, no more random strings)
• cleans up valid template checker
• cleans up the console output
• format the documents using ruff
• add an extra line to the filehandler writer, that way we can remove all the double empty lines in all templates
• update the workflow
• add a config DEFAULT object
• add prohibited arguments to templates
• refactor platform detection code
• refactor fp_template code
• n_runs only adds a _{{ run }} to the filename if n_runs is more than 1

I also structured a response to missing parameters. Since we assume our templates are correct, only custom templates can have missing parameters (parameters used in the template but not provided by the python class). Therefore, we can throw an error and assume the user is using the wrong base template with their custom template.

I've added a catch for if a user selects a base template that's not part of the 3 predefined base templates. Not possible under normal use, but if an extension adds a template to the base templates, this could happen.

Now the pipeline is:

1. cast base template to lower case
2. check if base template exists (if not, throw an error)
3. check if a custom template path is given
4. check if custom template path is valid
5. load the datasets
6. start the rendering

[PeterLombaers]

The README could probably use an update as well, in particular the section on making a custom template. You could now also do that via an extension, and using the TemplateBase class.

[PeterLombaers]

Everything seems to work well! The following comments I made could also be handled in separate pull requests.