Bugzilla

Add the [taskcluster task_id](https://github.com/mozilla/treeherder/blob/71b14c60785888c107b57bd6eaf56a20b79fd315/treeherder/model/models.py#L674) data to the alert summary API endpoint. This would help us getting the profile urls without [fetching the entire jobList‎](https://github.com/mozilla/treeherder/blob/71b14c60785888c107b57bd6eaf56a20b79fd315/ui/models/browsertimeAlertsExtraData.js#L32) in the frontend.
Also will help us being a step closer to getting the side by side task id directly in alerts view.

Add the [taskcluster task_id](https://github.com/mozilla/treeherder/blob/71b14c60785888c107b57bd6eaf56a20b79fd315/treeherder/model/models.py#L674) data to the alert summary API endpoint. This would help us getting the profile urls without [fetching the entire jobList‎](https://github.com/mozilla/treeherder/blob/71b14c60785888c107b57bd6eaf56a20b79fd315/ui/models/browsertimeAlertsExtraData.js#L32) in the frontend.
Also will help us being a step closer to getting the side by side task id directly in alerts view.
The field would go under [alertsummary api](https://treeherder.mozilla.org/api/performance/alertsummary/?id=38715) `["results"]["alerts"][alerts_id]` next to `"series_signature"`

Add the [taskcluster task_id and retry_id](https://github.com/mozilla/treeherder/blob/71b14c60785888c107b57bd6eaf56a20b79fd315/treeherder/model/models.py#L674) data to the alert summary API endpoint. This would help us getting the profile urls without [fetching the entire jobList‎](https://github.com/mozilla/treeherder/blob/71b14c60785888c107b57bd6eaf56a20b79fd315/ui/models/browsertimeAlertsExtraData.js#L32) in the frontend.
Also will help us being a step closer to getting the side by side task id directly in alerts view.
The field would go under [alertsummary api](https://treeherder.mozilla.org/api/performance/alertsummary/?id=38715) `["results"]["alerts"][alerts_id]` next to `"series_signature"`.

Currently, we include the profile links to the alert summaries by copying the summary from alerts view, but they are not included in the comment 0 of the regression bug. If we want to do this we’ll run into a big performance issue that will make the browser hang on the alerts view.

[This code](https://github.com/mozilla/treeherder/blob/8c98e98b6eef47995fa2730ae31778a0d39389fd/ui/models/browsertimeAlertsExtraData.js#L32) is fetching the entire push list twice for every alert item that needs the profiler links. The performance difference is from few milliseconds when copying a small alert summary for talos, to thousands of milliseconds (around 4 seconds in the simulation in the screenshots) for browsertime - where we use profiler links. If we do this for a page of alerts when we load the alerts view, it will simply hang the browser. So including the data we need directly into the API response of the alert items.