A chunk implementation that is much simpler and makes more sense. Everything is now in the ArchiveWriter + Selector

* Store subtables in chunks of 100 subtables per blob. Those 100 subtables are stored
  serialized as an array: array($subtableID => subtableBlob). The first 100 subtables are
  stored in "chunk_0", the next 100 subtables are stored in "chunk_1", ...
* Subtable Ids are now consecutive from 1 to X
* We do no longer serialize the whole Row instance when archiving, instead we only
  serialize the Row's array which contains columns, metadata and datatable. This is not
  only more efficient but allows us to refactor the Row instance in the future (although
  we will always have to be BC)
* Faster row implementation: Columns, Metadata and Subtables access is much faster now

refs #5940 moved files into a subfolder framework, added autoloader to remove duplicated code to load autoload.php and to be able to register more autoloaders (eg for test files) on demand. This I got read of many includes that had to be updated all the time and that had to be updated all the time when moving iles

refs #5940 we might stay backwards compatible this way for 2 months. moved some tests from unit to integration and explained when a test is a unit test, an integration test or a system test.

refs #5940 put tests in correct folders, better testsuite names, some tests still fail and I cannot figure out why

Refs #5800, add namespaces to integration tests in root folder. Also add IntegrationTestCase to a namespace, re-add individual test @groups, move test groups to class level, and rename test files & class names so underscores are not used.

Piwik is a free/libre analytics platform. Refs #4455 GNU Package requirement to use free/libre instead of open source

Fixes #4768 Implement performance improvement for period=range: do not archive sub-tables (only the parent table).
The sub-tables will be archived only when idSubtable is found, or flat=1, or expanded=1

Move UserCountry specific logic out of core tracker files and into UserCountry plugin and remove some uses of Zend_Registry in tests.

Converting Access & Auth to namespace

Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)

Notice that auto refactoring has created a nested namespace. Not sure this is what we want - so we might have to edit those nested namespaces afterwards (I think they don't look so good)

 * new segment 'siteSearchKeyword'
Fixes #3903, #3905:
 * adding few fields in the Live API output to accomodate getSuggestedValuesForSegment
 * renamed other fields for consistency with segment names
Fixes #3906:
 * new API: getSuggestedValuesForSegment which returns top suggested values for a particular segment. It uses the Live.getLastVisitsDetails API to fetch the most recently used values, and will show the most used values first

 * Adding tests for everything. The test case actually generates data for all segments so that VisitsSummary.get returns some data for each of the 47 segments being tested returns some data.
  How it works:
  * generate extended data in fixture
  * Tests (1) call getSuggestedValuesForSegment for each segment, check there is some data returned for each segment
  * get the first suggested value from the list,
  * Tests (2) call VisitsSummary.get with this segment value, eg. countryCode==ru.
    * I worked this way for all 47 segments until all tests had some data ==> now we know that all segments have been tested and that the auto suggest works for all segments. TDD FTW!

Converting Piwik core source files, PHP, JS, TPL, CSS

More info: http://piwik.org/participate/coding-standards/

Refs #2908, refactored tests so database setup (adding sites, tracking visits) are separated from API tests. Put setup code into fixtures and reused code as much as possible.