Fix multiselect population (Issue #333)

[driver-by]

I've added demo on multiselect page with buttons that populate multiselect with values.
Model formatter was changed to accept inputValues not only 'as' value, but the whole object. For example in this case:

<ui-select multiple ng-model="multipleDemo.populateSelection"...
   <ui-select-choices repeat="person.email as person in people...

According to old logic, we must populate multipleDemo.populateSelection with emails:

multipleDemo.populateSelection = ["[email protected]"];

Now we can do it like this:

multipleDemo.populateSelection = [{name: 'Adam', email: '[email protected]', age: 12, country: 'United States' }];

So, if we get it from the backend, we need not to repopulate our model with "correct" values.
Also I've added correct object comparison there.

Here is plunker from Issue #333. And this is forker version with fixed select.js

[scatcher]

Fixes issue in my tests.

[ArSoron]

Fixes issue for me. Seems to be the only way to get ui-select to load values into multiple ui-select with asynchronous lookup values request.

[PowerKiKi]

@driver-by, would you have to time squash, rebase and add tests for this ? Then I would merge it.

[driver-by]

@PowerKiKi, yes, I'll find time

[PowerKiKi]

Actually, I may have spoken too fast. I had a closer look at this, and noticed the usage of angular.equals may have a significant impact on performance if the objects compared have a deep structure. I believe this use-case can actually be fulfilled with a much lighter approach, by specifying what to compare. As done by @JeffGreat in #256.

I'm in favor of closing this, and focusing on #256

[driver-by]

Ok