Autocomplete: when using the keyboard to navigate the options, the currently focused item should be the 'selected' option

#### Bug, feature request, or proposal:
Feature request

#### What is the expected behavior?
When using the keyboard to navigate through the options, as the focus changes from one option to another, the selected option should be the currently focused option, thus following the "selection follow focus" principle as stated in the Material docs [here](https://www.w3.org/TR/wai-aria-practices/#kbd_selection_follows_focus).

If the desire is to leave the current behavior then at least provide an option to turn this behavior on.

#### What is the current behavior?
Using the keyboard to navigate the options does not automatically update the 'selected' option.

#### What is the use-case or motivation for changing an existing behavior?
Many users expect to be able to select an option by simply navigating the options without being required to press a particular key to indicate their selection. By simply leaving the current control after having navigating to a particular option, they assume that they have selected the option as well. The main example I have for this is using the TAB key. I often navigate options using the arrow key and then press the TAB key after having 'selected' my option using the arrow keys. The current behavior is such that you are required to 'select' the option using the ENTER key, otherwise the value is not set when you TAB away from the control.

Google's own search engine follows this principle. As you type in your search, Google begins searching for the phrase and provides several autocomplete phrases for you. If you navigate the provided phrases, the search results update based on the currently focused phrase without having pressed ENTER or another key.

#### Is there anything else we should know?
See [this](https://github.com/angular/material2/pull/4401) pull request for the initial discussion.

Beginne damit, den verknüpften Pull Request #4401 und die bestehende Diskussion mit 17 Kommentaren zu prüfen, um die ungeklärten Entscheidungen zum Verhalten zu verstehen. Verfolge anschließend die Implementierung von Angular Material autocomplete ausgehend von ihrem Component-Einstiegspunkt und ermittle dann, ob completion den Fokus der Auswahl folgen lassen sollte oder eine Option für dieses Verhalten bereitstellen sollte. Als erledigt gilt die Aufgabe, wenn das gewählte Verhalten implementiert und für die Navigation mit Pfeiltasten gefolgt von TAB verifiziert ist und der bestehende ENTER-Ablauf berücksichtigt wurde.

Vom Indexierungsmodell aus dem Issue-Text verfasst.