fix: ordering workspace projects that are in peer dependencies

[zkochan]

close #7813

[levrik]

Just this morning I fixed a cyclic workspace dependencies warning through peer dependencies but with this update is happens again. I don't know if peer dependencies not being included in the cyclic workspace check was on purpose or not.

Just to elaborate a bit on the setup I'm having: components has dependency on icons while icons has a dependency on components. This is done this way as icons uses the Icon base component from components but icons then includes a specific set of icons using this primitive component under the hood. components itself uses something from this icon set in some components so it has a dependency on icons. I thought defining components as a peer dependency in icons would be the correct solution which also removed the warning in 8.15.5 but started to re-appear in 8.15.6.

Now I wonder: Was using peers expected to allow such semi-cyclic dependency structures (making this a regression) or was it never intended do work like this (making this a fix also for a missing warning)?