This pull request is a replacement for #10374

This pull request extracts the HTTP profiler from the HttpKernel component to a new dedicated component: Profiler.

The goals are to improve the general architecture and usability of the component as stated by @webmozart ( #10374 (comment) )
as it stands now no BC is broken as the original DataCollectors are still supported by the new Profiler.

New DataCollectors and Profiler no longer require a Request.
DataCollectors are should be able to collect data from other sources, which will prevent some ugly hacks that were previously required, they will still require to listen to events to collect the data, I don't see a way around this, but this doesn't seem a big issue.

If a DataCollector requires the Request, it should have the RequestStack and get it from there, the Responses can be added just like Controllers are added, by subscribing to the Kernel Events.

$httpProfiler = new HttpProfiler($requestStack, $storageInterface);
$httpProfiler->addCollector(new RequestDataCollector($requestStack));
$httpProfiler->addCollector(new ExceptionDataCollector());
$httpProfiler->addCollector(new FormDataCollector());

// Runtime data is collected
$profile = $httpProfiler->collect();

$requestData = $profile->get('request');

// Late data is collected
$httpProfiler->save($profile);

Ideas

• rename Profiler::collect() to Profiler::profile() or other name that makes slightly more sense. (+ would help on BC)
• provide ConsoleProfiler, will require some interface changes to the WebProfiler or a console version

Todo's

• gather feedback for my changes
• add additional tests to increase coverage.
• add README.md
• submit changes to the documentation