As you mentioned these can be safely ignored. In many cases we (as in Strapi) didn’t define peer dependencies for various reasons. Given how old Strapi is we have several legacy packages and nested under several layers are simply older packages. Many newer ones install newer versions of these which get used by our older packages.
This is extremely common in node ecosystems and fixing it simply isn’t worth our time at the moment since they cause no errors (or when they do, we fix them). As you can imagine our team has higher priorities at the moment such as bug fixes that actually impact users and developing new features. Possibly when things slow down (or even just as we iterate on features and packages) these warnings will slowly fade away but for now they cause no problems and thus are not a concern.
Note that it’s practically impossible to clean these up from the project level and requires the “fixes” to be done on our Strapi packages.