Follow-up for #2663410: calling TypedConfigManager::getDefinition() causes cache pollution

Problem/Motivation

Discovered in 📌 Configuration schema & required keys Fixed .
🐛 TypedConfigManager::_getDefinitionWithReplacements() incorrectly replaces generic definition Fixed introduced a regression: it introduced a bug that made TypedConfigManager sensitive to cache pollution. In the
case of hitting the $type = "$type||$sub_type"; edge case, 2 calls to getDefinitionWithReplacements() happen:

Steps to reproduce

1. buildDataDefinition() calls it WITH the $replace parameter
2. getDefinition() calls it WITHOUT the $replace parameter

Calling getDefinition() causes the computed type to be overwritten.

Proposed resolution

Clearing the definitions cache is a temporary work-around:

$this->getTypedDataManager()->clearCachedDefinitions();

(after calling ::getDefinition(), to allow all subsequent typed config manager logic execution to work correctly)

Remaining tasks

Test coverage.

User interface changes

None.

API changes

None.

Data model changes

N/A

Release notes snippet

N/A