Allow for registering a new ConvivaAnalyticsIntegration to a reused Player

[kvolkers]

The current setup expects for 1 ConvivaAnalyticsIntegration instance to be used with 1 BitmovinPlayer instance.

To make it easier to get Conviva to track correctly in our implementation when changing video stream with 1 BitmovinPlayer instance (live channel zapping, play next, some use cases with chromecast) we'd like to use a new ConvivaAnalyticsIntegration for each new video stream.

The following changes were made:

• Add ConvivaAnalyticsIntegration.release(Boolean releaseConvivaSdk) function. Calling this function with releaseConvivaSdk = false prevents ConvivaAnalytics.release() from being called. Otherwise creating a new ConvivaAnalyticsIntegration right after this would result in a broken session ending in an EBVS.
• Detach Bitmovin player event listeners on ConvivaAnalyticsIntegration.release(Boolean releaseConvivaSdk).
• Add ConvivaAnalyticsIntegration.release() convenience function mimicking current behaviour for backwards compatibility.

I couldn't get all tests to work, but I suspect this might be an issue with the 2 tests itself, report included. androidTests.zip

[CLAassistant]

All committers have signed the CLA.

[dweinber]

For the record: I merged this into develop and re-ran the tests on my main dev device successfully: