If core provides a more recent version of a module use it instead of contrib

I can't remember the specific issue, but I think this is handled by composer provides now?

I found this: https://stackoverflow.com/questions/68667235/what-does-the-composer-prov... but no documentation on composer directly.

Can we close this then?

I thought so, but I can't actually find a usage of composer provides in core, I did find 'replaces' but we're not using that for any core modules. Maybe I was thinking of 'replaces' and provides is an old alias.

Ohhh... except now I've written all that out, this is controlled on the Drupal.org side e.g. when we move modules out, we have to file an issue to free up the contrib namespace, like 📌 Ensure that Book does not get special core treatment Needs review .

When a module is brought in the same should happen - can't remember we moved in an identically named project though since big_pipe.

So this is possible afaik and implemented somehow, but maybe it could use some documentation somewhere?