anchor.diff:  ==== `collectors` Section
   
   The Collectors portion of the response shows high-level execution details. Lucene works by defining a "Collector"
  -which is responsible for coordinating the traversal, scoring and collection of matching documents.  Collectors
  +which is responsible for coordinating the traversal, scoring, and collection of matching documents.  Collectors
   are also how a single query can record aggregation results, execute unscoped "global" queries, execute post-query
   filters, etc.
   
  
positive.code: 
  From the profile structure we can see that the `my_scoped_agg` is internally being run as a `LongTermsAggregator` (because the field it is
  aggregating, `likes`, is a numeric field).  At the same level, we see a `GlobalAggregator` which comes from `my_global_agg`.  That
  aggregation then has a child `LongTermsAggregator` which from the second terms aggregation on `likes`.
  
  The `time_in_nanos` field shows the time executed by each aggregation, and is inclusive of all children.  While the overall time is useful,
  the `breakdown` field will give detailed stats about how the time was spent.
  
negative.code: 
  `score`::
  
      This records the time taken to score a particular document via its Scorer
  
  `*_count`::
      Records the number of invocations of the particular method.  For example, `"next_doc_count": 2,`
  