Given the above and the implication of this plugin in issues like https://github.com/magento/magento2/issues/34325#issuecomment-942231971 can someone please confirm if there is any benefit of this plugin above what Composer 2.0 does? If there is none I would propose to make this plugin a No-Op on Composer 2.0 (and subsequent removal once only Composer 2.0 is supported) and keeping the functionality when using Composer 1.0.
I believe this plugin's aim is to guard against unintentional switching of the repository source.
Composer 2.0 uses canonical repository order by default - see https://getcomposer.org/doc/articles/repository-priorities.md#canonical-repositories this prevents unintentional switching of repositories.
Given the above and the implication of this plugin in issues like https://github.com/magento/magento2/issues/34325#issuecomment-942231971 can someone please confirm if there is any benefit of this plugin above what Composer 2.0 does? If there is none I would propose to make this plugin a No-Op on Composer 2.0 (and subsequent removal once only Composer 2.0 is supported) and keeping the functionality when using Composer 1.0.