Move Custom Nodes to regular libraries tree

#### Modifications

Nodes under "Addons" header are moved to regular libraries tree. For both views: library view and search results.

##### Before
![001](https://cloud.githubusercontent.com/assets/8158551/5106932/e97b355a-7005-11e4-8c17-6417fc03eb0d.PNG)

##### After
![002](https://cloud.githubusercontent.com/assets/8158551/5106940/f4779624-7005-11e4-907a-34acabb626c4.PNG)

#### Modifications

All nodes are added using `BrowserCategoriesBuilder`. Removed some code which are special for addons representation.

#### Additional references

[MAGN-5483](http://adsk-oss.myjetbrains.com/youtrack/issue/MAGN-5483).

There will be removed more redundant code as EB said he liked it. The task for it: [MAGN-5484](http://adsk-oss.myjetbrains.com/youtrack/issue/MAGN-5484).

#### Reviewers

@Benglin, please, take a look.
We have three different ```ListBox``` child for a ```LibrarySearchView```: ```topResultListBox```, ```MemberGroupsListBox```, and ```MembersListBox```. Does that means we will always get ```topResultListBox``` when the search result changes? Another question is, ```HighlightedItem``` seems to be ```ListBox``` here, but it can be ```ListBoxItem``` in some other places in this file. Is that correct or desirable? Don't we always want ```HighlightedItem``` to be a ```ListBoxItem```?