While working on #31353, I noticed that the alias resolution error message in SimpleAliasRegistry is misleading.

Specifically, when a resolution conflict is detected, the resolveAliases(StringValueResolver) method throws an IllegalStateException stating that the resolved alias is already registered for the registeredName; whereas, it should state that the resolved alias is already registered for an existingName.