Calling TypedConfigManager::create() does not use the definitions of TypedConfigManager (config schema), but of TypedDataManager (field types)

I think we should add explicit test coverage for all methods on TypedConfigManager, because it's unclear which code paths work correctly and which ones fail in the way described in the issue summary and demonstrated in the basic test coverage already in the MR.

The test added seemed to work. Not sure if this issue is meant to include all test coverage or if that should be a follow up. Could that be noted in IS?

I think the plan is to include all test coverage in this issue, I think that would make the most sense?

Bumping to given the data corruption/pollution nature of the problem.