Component with higher priority is not taking precedence when deployed as an extension

Steps to reproduce

• Create a Java component with the same hint as another existing one but with higher priority (e.g. 900, as described on the Component Module documentation).
• Deploy the component as a JAR in WEB-INF/lib: as expected, the component is taking precedence over the one having default priority.
• Remove the component JAR from WEB-INF/lib and restart the server.
• Deploy the component as an extension via the extension manager, from a local Maven repository.

Result

The component seems to be ignored by XWiki while one would expect that it overrides the component having the same hint and default priority.

Example

I might be overlooking something, but I encountered this issue when deploying the Ring extension in XWiki Standard 11.10. In order to possibly observe the behaviour of another component in the same situation, I tried to identify other components provided by XWiki Standard with higher priority than the default one and deployed as a JAR extension by default but I couldn't find any so far.