Add coordination time to profiler

Describe the bug
Took time on profiled request is 1.3 seconds, inspecting the shards search/aggregations times they are all under 460ms-339ms. This implies coordination had a substantial impact on the response time.

To Reproduce
Steps to reproduce the behavior:

1. Take a query from your ES instances slow log
2. Repeat the query with "profile":"true" until took time is above an acceptable threshold
3. Investigate the response by computing per shard - query / rewrite / collector time
4. Print the list of shard based times
5. Look for the 'longest running shard' to determine the bottleneck
6. Inspect the the coordinated time breakdown

Expected behavior
There would be a breakdown for coordination

Plugins
N/A

Screenshots
N/A

Host/Environment (please complete the following information):

• OS: Linux x64

Additional context
In some ways this is a feature request - but this is also an incomplete scenario to diagnose performance issues with this existing profiling tools.

Start by reproducing the issue with a slow-log query and "profile":"true", then compare the total took time with the per-shard query, rewrite, and collector timings. Trace the profiler's coordination path and define the breakdown needed to account for time not attributed to individual shards. Done means the profile response reports coordination time alongside shard-based timings.