Call out v0 to v1 changes

[stramel]

It would be nice to have linter warn and be able to fix some of the easy v0 to v1 spec changes with some Polymer changes that would allow Polymer v1 (P1) components to work with Polymer v2 (P2) legacy. These changes should allow P1 components to work with P2 without going into the full hybrid setup.

CSS

• @apply(--foo); to @apply --foo;
• var(--a, --b) to var(--a, var(--b))
• :root to html or :root to :host > * depending on location (shadow root vs main document) (Added a polyserve option doNotCompile and speed up WCT tests #168)
• ::content to ::slotted ([analyzer] support all default param types #160)
• ::shadow and /deep/ removed (pull-all.sh should not have dependencies #6) ([cli] test: Pass moduleResolution option from config to WCT. #158)

HTML

• <content> to <slot> (Currently listed under Polymer)
  • Warns
  • Fixable
• <style> tags moved inside <template>

Polymer

• document.createElement('style', 'custom-style') not allowed anymore (Fix CLI gulp script. #163)
• is="custom-style" to be wrapped with <custom-style> if not within <template> (Prepare releases. #155) (Use a single shared top-level tslint #166)
• Check that dom-module has id attribute instead of is or name
  • Warns
  • Fixable ([cli] init: Add an option to init from the Polymer 3 compatible PSK prerelease. #162)

Possible Additional ones
Ensure semi-colon on CSS Mixin declarations
Polymer.dom returns NodeList instead of Array (NOTE: May be difficult to detect)
:host-context([dir=rtl])) to :dir(rtl) (NOTE: Only available in Firefox)
lazyRegister no longer exists (NOTE: Not sure this should be a lint rule)
this.customStyle['--my-toolbar-color'] = 'blue'; to this.updateStyles({'--my-toolbar-color': 'blue'});

[stramel]

This covers the majority of v0 to v1 changes.

[rictic]

Awesome work @stramel!!