Infrastructure repo for multiple repository setup

[neanias]

I've found a couple of issues (#4982, #5395) about managing Copilot apps across multiple repositories. The general suggestion seems to be having an infrastructure repo that holds environment information and then leaving service configuration in the relevant repos (e.g. frontend, backend). Should pipeline definitions also go into the separate infrastructure repo or should it be kept with the relevant service?