Support incremental-max and sample in Profiler data

I also did some cleaning and refactoring in
tracked_objects.  We had a lot of functionality that
has migrated to JS, that we didn't need (a lot of
acccessors that are supplanted by the ToValue()
methods.

I'm anticipating that we'll move to an asynhcronous
collecting of data from the profiler, so that we can
bounce around to various threads and more cleanly
collect samples (without risking races during
data snapshots).  Several of the refactors are
heading in that direction.

r=rtenneti
tbr=jam (for microscopic content change)
BUG=106291,106293
Review URL: http://codereview.chromium.org/8775061

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112928 0039d316-1c4b-4281-b951-d872f2087c98

chrome/browser/metrics/tracking_synchronizer.cc

@@ -245,7 +245,7 @@ int TrackingSynchronizer::RegisterAndNotifyAllProcesses(
   content::ProfilerController::GetInstance()->GetProfilerData(sequence_number);
 
   // Send profiler_data from browser process.
-  base::DictionaryValue* value = tracked_objects::ThreadData::ToValue();
+  base::DictionaryValue* value = tracked_objects::ThreadData::ToValue(false);
   const std::string process_type =
       content::GetProcessTypeNameInEnglish(content::PROCESS_TYPE_BROWSER);
   value->SetString("process_type", process_type);

content/common/child_thread.cc

@@ -232,7 +232,7 @@ void ChildThread::OnGetChildProfilerData(
     int sequence_number,
     const std::string& process_type) {
   scoped_ptr<base::DictionaryValue> value(
-      tracked_objects::ThreadData::ToValue());
+      tracked_objects::ThreadData::ToValue(false));
   value->SetString("process_type", process_type);
   value->SetInteger("process_id", base::GetCurrentProcId());