fix(progressLinear): sync logic, perf upgrades, fix animations

[ThomasBurleson]

synchronize progressLinear with similar logic used in progressCircular.

• improve animation performances
• watch md-mode for changes
• refactor animation SCSS
• enable hiding and no-animations with undefined/empty md-mode attributes
• for both indicators, use display:inline-block;
• update demos with enable switch
• fix query mode
• update Select to use enhanced progressCircular component
• fix autocomplete styling of progress-linear.md-mode-indeterminate

BREAKING-CHANGES

Before:

md-progress-linear {
  display: block;
}
md-progress-circular {
   // display not set
   // position not set
}

md-progress-linear {
  display: inline-block;
  position: relative;
}
md-progress-circular {
  display: inline-block;
  position: relative;
}

Fixes #4421. Fixes #4409. Fixes #2540. Fixes #2364. Fixes #1926. Fixes #3802.

[ThomasBurleson]

@robertmesserle, @topherfangio - ready for review.

[topherfangio]

Will dig into the code changes shortly, but when running locally, I noticed a small issue:

1. Open either of the Progress Linear or Progress Circular demos
2. Turn off the animations using the On/Off toggle switch at the bottom
3. Switch to the other demo
4. Sometimes, the TypeError: Cannot read property 'runner' of undefined error is thrown

It appears identical to issue #4388.

Originally, it seemed to happen every time I switched the demos, but since your (now next to latest) commit, it seems to happen less.

[topherfangio]

Is there a particular reason why the formatting has extra indentation here?

Also, should it be mode() === MODE_DETERMINATE (i.e. with the triple =)?

[robertmesserle]

Actually, contrary to what most of the JS world says, the Google JS styleguide uses == instead of ===. I struggle to break the === habit on this project. =p