Create tool for splitting RepositorySettings into component specific parts

As result of out discussions about how to ensure a safe and robust creating, distribution and installation process for the permission model included in the CollectionSettings. The primary concern (after a lot of discussion) was the dynamics involved in defining client permission should only be distributed to relevant components, eg. pillars and perhaps services.

A flexible and easy solution is then to generate component specific CollectionSettings based on the master CollectionSettings. The differs from the current solution, where the full CollectionSettings are shared across all components.