Clean up configurations to utilize composition instead

[t-persson]

Applicable Issues

Description of the Change

With my change for controller I noticed that I had to add a lot of the same code in multiple places. By utilizing composition here instead we will get cleaner code and it makes it easier to add new base configuration values instead of having to add it to every config separately.

Alternate Designs

Considered keeping it as is, but I think it's better to try and fix this now when it is easy instead of waiting and, potentially, not being able to.

Possible Drawbacks

I don't see any drawbacks of this design.

Sign-off

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

Signed-off-by: Tobias Persson [email protected]

[fredjn]

Why remove the tests for specific configurations?

[t-persson]

The test mostly just test that it is possible to use the config interface. It does not necessarily test that each value is possible to set.
While a new config_test could be added for the executionspace config it would not really do anything other than check that the default values are correct. The benefit of adding it would be that we'd be able to check that it loads the base config, but loading the base config is not really necessary as long as the config implements the Config interface (which it does).

In other words: I can add the tests if we want to, but I don't see much value in having them.

[t-persson]

Forced push due to rebase