IContentProvisioning requires streamId in its methods.

startStream(int streamId) is accessible through:
HTTP POST at ${ws.rest.url}/contentprovisioning/{streamId}

stopStream(int streamId) is accessible through:
HTTP DELETE at ${ws.rest.url}/contentprovisioning/{streamId}

Given streamId is used to identify the content the media server should send.

Current implementation of ContentProvisioning allows only one simultanieous stream being active.
Calling startStream while ContentProvisioning is streaming, will fail (despite given streamId).
Merge branch 'demo/tnc-2014' into feature/streamId-in-content-provisioning-interface

Conflicts:
	extensions/bundles/contentprovisioning/src/main/java/org/opennaas/extensions/contentprovisioning/ContentProvisioning.java

Conflicst solved manually.
Merge pull request #925 from isartcanyameres/feature/streamId-in-content-provisioning-interface

Feature/stream id in content provisioning interface