BrowseDefinition should be split up in to normalized and client-side models

BrowseDefinition is used both as the model for the rest response, and as the model to use in the rest of the angular app.  For every other model these are split in to two classes.  Even if they would be identical, for consistency's sake it would be better to split BrowseDefinition up as well.