Refactor Results To Support Subbasin
Refactor Results To Support Subbasin

* Add a 'subbasin' result to the gwlfe result collection

* Set polling, error and results on ResultModels
  based on whether the fetch request was in subbasin mode or not

  For example, when fetchResults is run outside of subbasin mode,
  only runoff and quality should have 'polling', 'error', and 'results'
  set by the task helper. When run in subbasin, only the 'subbasin'
  result in the collection should get those attributes touched.

* Add and set error attributes (subbasin_ and regular) on the scenario
  for mapshed errors. Error during mapshed will
  cause "gathering data' to spin indefinitely -- we can use these
  attributes in the views to prevent this.

* Don't kick off subbasin modeling every time fetchResultsIfNeeded
  is called in subbasin mode. Check if the subbasin result model has
  results.

WikiWatershed/model-my-watershed,WikiWatershed/model-my-watershed,WikiWatershed/model-my-watershed,WikiWatershed/model-my-watershed,WikiWatershed/model-my-watershed