Changed JavaScript Tracking Code generation to use "//", instead of verifying whether the site is using "https", or not, and generating a corresponding URL.

"//" has been part of the RFC for well over 18 years. It has been confirmed to work in all major browsers (Firefox, Chrome, IE, Opera).

References:
- RFC 1808 Section 4: http://www.ietf.org/rfc/rfc1808.txt
- RFC 3986 Section 5.2: http://www.ietf.org/rfc/rfc3986.txt
- Stack Overflow QA 1: http://stackoverflow.com/q/4659345/238722
- Stack Overflow QA 2: http://stackoverflow.com/q/6785442/238722
First attempt at fixing failing tests.
Merge branch 'master' of https://github.com/piwik/piwik
Missed one correction on the failing tests.
refs #4996 track content pieces and display a content report under action and added a widget
refs #4996 actually archive the tracked data and display the actual data in a report
fix plugin name [ci skip]
updated questions #4996
refs #4996 just read in the specs only the name is required
Merge branch '4996_content_tracking' of github.com:piwik/piwik into 4996_content_tracking
refs #4996 some thoughts on piwik.js
refs #4996 better naming
refs #4996 some more questions
refs #4996 some more questions about content tracking
refs #4996 thoughts on how to define content and already started to create some needed methods
some clarifications in doc [ci skip]
moved markup into its own section [ci skip]
Replying to first questions, refs #4996
Replying to next questions, refs #4996
refs #4996 archiving of impressions should work now, displaying impressions should work (contentName => contentPiece and contentPiece => contentName). Next step: Matching interactions with impressions then this part is nearly done hopefully