Let server manipulate `Composition`s

• Remove saveLayout function, as now Blending Editor, should be responsible for that.
  Starcounter/Blending#471
• Drop support for compositionProvider.Composition, only compositionProvider.Composition$ is supported
• Element observes Polymer notifications for compositionProvider.Composition - to be able to react on server-side changes triggered by any means, not just composition editor custom element.
• Save updated compositionProvider's custom composition as stored one, even if it's the same as current temporary one, as after closing the editor changes were reverted not to the saved state, but to the state before editing was started Starcounter/Blending#460
• more verbose partial attribute deprecation warning - now it shows a reference to the problematic instance

Compatibility with new composition editor solution

Added compatibility with new composition editor with respect for backward compatibility.
Related Blending app changes: https://github.com/Starcounter/Blending/pull/395

Render blocking styles, more radical warning

• element is now hidden until all links in given shadow DOM composition are (successfully or not) loaded #111, see README.md#render-blocking-links for more
• warning about non-namespaced view-model is now more intrusive and renders red border around partial view #114

Ignore package-lock.json in bower.json

5.1.1

Version 5.1.1

Parent (host) compositions

Added support for compositions (presentations) provided by the parent (host) view - the view that uses <starcounter-include> to stamp the partial one.

You can now do:

	<starcounter-include slot="timeline/new-events" view-model="{{model.NewEventActions}}">
		<!--
		starcounter-include takes as shadow root:
		merged `template is="declarative-shadow-dom"`s < `<template is="declarative-shadow-dom" TBD-host>` content < .CompositionProvider.Composition$ (`<template is="..." solution>`)
		-->
		<template is="declarative-shadow-dom" presentation="parent">
			<uni-magic-menu><slot></slot><slot-all></slot-all></uni-magic-menu>
		</template>
		<!--
		Content that will be loaded from the merged view:

		<a href='' slot="calendar/new">New event</a>
		<a href='' slot="calendar/newrec">New recurring event</a>
		<template is="declarative-shadow-dom" >
			<paper-menu>
				<slot name="calendar/new"></slot>
				<slot name="calendar/newrec"></slot>
			</paper-menu>
		</template>
		<button onclick=""></button>
		<note-widget slot="notes/new"></note-widget>
		<template is="declarative-shadow-dom" default>
			<ul>
				<li>
					<slot name="notes/new"></slot>
				</li>
			</ul>
		</template>
		-->
	</starcounter-include>

To distribute all named slotables regardless of their slot name, use <slot-all> custom element

See #102 for more details.

Update deps for better security

5.0.1

Version 5.0.1

Remove deprecated starcounter-composition and deprecate `partial` attrib

• Drop starcounter-composition support #91
• Remove v0 <-> v1 translation features a1731a7
• Use latest jargon in docs and code #86
• Deprecate partial attribute in favour of viewModel (prop) and view-model (attribute).

Prepare for working with BlendingProvider

• Unhardcode CompositionProvider namespace, #79, #80
  Now, you can set it either per instance: scInclude.compositionProvider = "CustomNameSpace_7" or change the prototype: customElements.get('starcounter-include').prototype.compositionProvider = "CustomNameSpace_7" to affect all.

Cross-browser support (almost)

• Element works back again in polyfilled browsers. There is still an issue pending that may cause FOUC in some border cases,
• Race-condintion (#71) is now fixed.

Fix race-condition by setting template.href redundantly

More info in #71