Add h5 to testrunner and use static libraries in debug mode

[jbreue16]

To expand our tests (as proposed in #167 ), we want to use the standard CADET setup files in .h5 format for our reference solutions.
To read from h5 files in our tests, we include the h5 lib in the testrunner target.
We additionally link to static libraries to ease the use of debug builds.

[ronald-jaepel]

Alright, with this Pipeline we at least know, that the problem isn't in the CmakeSettings.json.
Apparently adding list(APPEND TEST_HDF5_TARGETS testRunner) alone breaks the CI. I don't have time today but hope I can look into this on Wednesday.

[jbreue16]

@ronald-jaepel Do we want to keep the static linking in debug mode?

[ronald-jaepel]

Here's a blog post about static vs dynamic. It contains everything I know about the subject. :D AFAIK the main drawback of static links is:

1. we potentially use more disk space
2. if we want to update a dependency we need to rebuild CADET

I think both of those are non-issues for us, so I'd vote for keeping it statically linked. It solves all of those "Can't find x.dll" errors.

Edit: found another drawback:

Static linking is generally slower at build time, which can be annoying in an edit-build-debug cycle. Mergeable libraries behave like dynamic libraries in debug mode.

[jbreue16]

I agree to trade this potential drawback at buildtime for resolving the "Can't find x.dll" issues.
Ill ask @schmoelder for review, maybe he has the same opinion on this?

[schmoelder]

I don't know enough about dynamically/statically linked libraries, and even less so for Windows, so take my opinion with a grain of salt.

• we potentially use more disk space

I don't see any issue here

• if we want to update a dependency we need to rebuild CADET

So be it. We're just talking about debug mode here, right?

[ronald-jaepel]

Yes, just the debug mode. The release build is statically linked anyways and has afaik always been.

[jbreue16]

Alright, lets merge this then.
This PR is a prerequisite for #167 :)