• Please check if the PR fulfills these requirements
• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit-message-format
• Tests for the changes have been added (for bug fixes / features)
• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  This fixes a current bug where objects set as option values and/or [(ngModel)] on select tags are converted to [object Object] strings.
• What is the current behavior?

For the following:

@Component({...})
class MyComp {
   selected: any;
   options: any[] = [
      {name: 'Pepper'},
      {name: 'Salt'},
      {name: 'Paprika'}
   ];

   constructor() {  this.selected = this.options[1]; }
}

<select [(ngModel)]="selected">
   <option *ngFor="#current of options" [value]="current">{{current.name}}</option>
</select>

You might expect the select to display "Salt", but it displays "Pepper" because all option values are set to [object Object]. When selecting new options using the dropdown, the selected property on the component class is set to [object Object].

This PR allows you to write the above code and have the selection updated on both ends as expected.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  No breaking changes.