move PathConfig tools to util::PathConfig

[jurgenvinju]

Is your feature request related to a problem? Please describe.

util::Reflective is not a cohesive module; the features don't have a lot to do with eachother, and the PathConfig functionality is becoming extensive and extensively used. Before it is "too late" and PathConfig is used by many DSL projects, I'd rather separate it from util::Reflective.

Describe the solution you'd like

Separate out the PathConfig features into an independent module, change the compiler to import this new module instead of util::Reflective.

Describe alternatives you've considered

Leaving it as is is also workable.

Additional context Add any other context or screenshots about the feature request here.

[jurgenvinju]

• Would also like to split generic PathConfig functionality, that fits every language from Rascal-specific compiler and interpreter configuration functionality, into a separate module
• Discuss about MANIFEST.MF and RASCAL.MF functionality. We could have a util::Manifest module that has the generic features and merge the RASCAL.MF and Rascal-specific PathConfig features into lang::rascal::util::ProjectConfig?