Content repository should not be cross cutting

Currently the content repository is using the BLS and BCS to get substitution parameters, doing substitutions, updating customization records, bypassing customization records of things like business name, and generally cross cutting concerns with most of the rest of the system.

The content repository should do nothing except retrieve content from the repository and return it. Any business logic related to substituting tags, applying customizations, or persisting customization records should be handled by services that are already cross cutting between applicable services.

ADS, SGS, SS-UI should be handling all these things. These are the services that manage business logic and behavior. They should be pulling unmodified, unsubstituted content from the CRS and applying customizations retrieved from the CMS(ContentModelService) then substituting the BusinessArea and location descriptions from the BLS and BCS and using the content appropriately. These services(ADS, SGS, SS-UI) are cross cutting in nature. The CMS, CRS, BLS, BCS are single concern services which should not be implementing cross cut business logic.