Feature: Sidenav or Route Scroll Service

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

#### What is the expected behavior?
Using a common native API call to `window.scrollTo(0, 0)` or doing something similar on the document body, etc would allow for scrolling the page to the top after a route ends when using a `sidenav`, otherwise the next view starts at the same position in the page.

#### What is the current behavior?
Routing between views within the sidenav content maintains the same scroll position assuming the content is the same length.

#### What are the steps to reproduce?
Add a sidenav and try to scroll to the top of the page anywhere at anytime. Eventually, I figure out this solution and stuck it in my `app.component`.

```
this.router.events
.filter(event => event instanceof NavigationEnd)
.subscribe(() => {
const contentContainer = document.querySelector('.mat-sidenav-content');
if (contentContainer) {
document.querySelector('.mat-sidenav-content').scroll({ top: 0, left: 0, behavior: 'smooth' });
} else {
this.window.scroll({ top: 0, left: 0, behavior: 'smooth' });
}
});
```

#### What is the use-case or motivation for changing an existing behavior?
Routing between views within the sidenav should be able to start at the top of the page, which is a common use case. Also, scrolling a browser using the native API has been around forever so it's a bit confusing when you expect it or one of the many variations of scrolling to work and they don't.

#### Which versions of Angular, Material, OS, browsers are affected?
Angular 4.0.2
Angular Material 2.0.0-beta.3

Inizia con il workaround di app.component mostrato nell’issue, in particolare router.events e NavigationEnd, e verifica in che modo .mat-sidenav-content gestisce lo scorrimento. Determina il punto di ingresso appropriato per i cambi di route e verifica che la navigazione tra le viste sidenav reimposti all’inizio la posizione di scorrimento del contenuto, senza includere il contenuto di sidenav. Non è indicato alcun file di test specifico, quindi aggiungi o individua una coverage per la navigazione tra le route e il comportamento dello scorrimento.

Scritto dal modello di indicizzazione a partire dal testo della issue.