• 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
• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Changes name of option value binding from ng-value to ngValue.
• What is the current behavior? (You can also link to an open issue here)
  Old code you'd write for option values that are objects:

<select [(ngModel)]="selectedCity">
   <option *ngFor="#city of cities" [ng-value]="city">{{city.name}}</option>
</select>

class MyComp {
   selectedCity: Object;
   cities: Object[] = [
      {name: "SF"},
      {name: "NYC"}
   ];
}

• What is the new behavior (if this is a feature change)?

New code you'd write for option values that are objects:

<select [(ngModel)]="selectedCity">
   <option *ngFor="#city of cities" [ngValue]="city">{{city.name}}</option>
</select>

class MyComp {
   selectedCity: Object;
   cities: Object[] = [
      {name: "SF"},
      {name: "NYC"}
   ];
}

• Does this PR introduce a breaking change?

Yes, technically, but ng-value was introduced 10 minutes ago.