feat(subheader): add subheader component

This implements #216.

As per suggestion from @matsko, uses native position: sticky when possible, otherwise uses a javascript implementation using the new $materialSticky service.

A new directive material-sticky is also exposed, which uses the $materialSticky service.

This pull request also makes the material-subheader create a h2 for accessibility purposes as per @marcysutton's suggestion. Subsequently, it ups the h2 and h3 in material-list-item to h3 and h4 respectively.

Commit messages have been squashed

Would love suggestions from @ajoslin on ideas for testing $materialSticky service, or anyone else who has ideas.

Also does anyone have opinion on whether we want to document material-sticky directive / $materialSticky service for usage on the docs?

Is there a less expensive way to do this? I don't like doing this every time a new subheader is added - I'm almost sure it will add some noticeable milliseconds to a page's initial compile time.

What if we only ran `scanElements` at the end of a digest?

That is, after a page is compiled and `registerSticky