This holds the main data of jobs and pushes for Treeherder, so it's a more complex model, basically. We will need to determine how much to continue storing in here vs. just in the state of the PushList component. Part of the overall conversion to ReactJS. Estimated difficulty of 7

Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/68f6001822ec20fb9403cc87f72f863ff0d4fb31 Bug 1450040 - Replace ThResultSetStore with Pushes context (#4102) * Switch from using job.result_set_id to job.push_id * Switch to using template strings for aggregateIds * Fix notification where selected job not in push range * Fix push status notifications(watching) to use safe React lifecycle method * Fix some lodash _ imports to specific file imports * Remove last usage of globalFilterChanged event * Rename usage internal to PushJobs from "platforms" to "filteredPlatforms" This takes what ThResultSetStore used to do and moves it to a React Context called "Pushes.jsx" and into the "Push.jsx" component to manage its own jobs.