SONAR-1922 Add a kind of version control for quality profiles

SONAR-1922 Add a kind of version control for quality profiles

Apply patch, which was contributed by Julien Henry:

* Following algorithm was implemented: Every profile starts with
  version=1 and used=false. As soon as there is an analysis of a
  project, the involved profile is set to used=true. Every modification
  to a quality profile (activation, deactivation or modification of
  rule) is logged in DB in dedicated tables. When a modification is done
  on a profile that is used=true, then version number is increased and
  profile is set to used=false.

* Introduced new metric to store profile version, which was used during
  analysis.

* If profile for project is different than the one used during previous
  analysis, then event would be created.

* Introduced new tab 'changelog' for profiles.

Following fixes were applied on original patch:

* Index name limited to 30 characters in Oracle DB, so names were
  reduced.

* Field ActiveRuleChange.profileVersion never read locally, because
  ruby read it directly from DB, so getter added.

* Direction doesn't make sense for 'profile_version' metric, so was
  removed.

* Fixed ProfileEventsSensor: it seems that TimeMachine not guarantee
  that the order of measures would be the same as in query, so we should
  perform two sequential queries.

* Fixed handling of null values during migration.