Update replace section for 2.4.5

[peterjaap]

A lot of bundled extensions have been removed by Magento

[jissereitsma]

Actually, this will render the new releases incompatible with Magento 2.4.4 and older. I'd rather keep the wildcard in there. Also, the additional replace rules that are no longer needed for 2.4.5+ are not harming either (replacing something that is not there, still results in a non-existing package). What do you think?

[peterjaap]

Aah right, that's how you approach this.

I was thinking about adding a tag per Magento version, but this would work too. Only problem with this is the current situation where there are hard-coded dependencies like yireo/magento2-replace-core#14 (comment).

If you would have a tag per Magento version, you could workaround this for a specific version.

[jissereitsma]

Yes and no. I've used separate branches per Magento version in the past, but this became a nightmare on its own to manage. Most problems arise not because of the composer replacements not working, but because of Magento code screwing up. But this is still nothing compared to the major issue of one replacement conflicting with another. As of yet, I'm more in favor of entirely new approach - to calculate the replacements based on some rules and then regenerate a new composer.json in the root alltogether.