periphery Move Configuration to separate module

I decided to separate Configuration and here is why. First of all, it's a big piece of logic. And it should be well separated. Also I'm planning to make it start point in public API. So the scheme would be like that: User -> Setup Configuration -> Launch ProjectDriver to the project -> Got SourceGraph and can analyze anything he wants.

For that purpose Configuration should be separated in different module. Because of that, Its needed to make some moves around (because cycling dependencies) BaseLogger -> SeparatedModule Logger, Glob, Shell, SwiftVersion, SwiftParser -> Utils Configuration -> SeparatedModule

Aug 21 '24 20:08 rofle100lvl

@ileitch What do you think about scheme for public API use?

Aug 21 '24 20:08 rofle100lvl

@ileitch Can you check it? New and new conflicts will appear. And also I have a talk in october and by this time i really want to move my project from fork to spm dependency...

Aug 28 '24 07:08 rofle100lvl

I've implemented this in https://github.com/peripheryapp/periphery/pull/817 as I took a slightly different approach, but thanks for the contribution all the same!

Sep 15 '24 22:09 ileitch