Adding security to the BCC for the search repository

The only missing piece is an xml file we need to load into ATG with the user generation. I have it in place but didn't commit it in this branch. 

I defined the basic rules for all the items in the search repository. The approach we have also allows us to define custom ACL's for specific items: I.E. the default boost rule.  This custom rules can be specified either via liquibase or via an xml that we load into ATG.

Once we have done a build with this initial changes, loaded the user creation xml and run this initial liquibase changes, we can start adding the custom rules for the items we consider necessary.