Fully implement US4, various recurring goal & testing improvements

[otisdog8]

Abstract

This finishes the backend for the tomorrow subsystem, and fills in the tests.

Issues

Closes #81

Type of Change

• New feature (non-breaking change which adds functionality)

Testing

Tests were written for the tomorrow filter

Checklist

• The code is understandable.

  • The code is follows formatting conventions (spacing, indents, etc).
  • The code makes use of names that sound like behavior.
  • The code is commented in hard-to-understand areas.
  • The code contains changes to documentation if needed.

• The code is well structured.

  • The code is organized into logical components.
  • The components sound like the behavior (requirements) they implement.
  • The components have clearly defined single responsibilities.

• The code is correct.

  • The changes include tests that prove the fix is effective or that the feature fully works.
  • The changes generate no new failed tests, build errors, or warnings.

Pending Items

No

[ZenoCS-Git]

Not sure if we should have a separate file for these time related test

[otisdog8]

we really need a label that makes tests run

[emguz]

Good job covering the case where we try finishing a goal in tomorrow when the same goal is in the today view. Nice exhaustive tests.