Issue #268 & 284 - support earliest start date & task due dates stored in the database

[nikotj1]

Description:

Issue #268:

Added earliest start date as a parameter for the smart scheduler. The purpose of this parameter is so that tasks are not scheduled right after a task is made, giving the user time to start the task at a later time instead of as soon as possible.

Issue #284:

Discovered that due dates could not be considered as it was no persistent, thanks @Minus20Five @HarrisonLeach1 #274.

Added dueDate field in:

• doto-backend/src/models/Task.js
• doto-backend/src/routes/task-route.js
• doto-backend/src/routes/task-route.js

Related to #273 @Kalashnikkov

Closes #268 and #284

• [x] The pull request is complete according to the following criteria:
  • [x] Acceptance criteria have been met
  • [ ] The documentation is kept up-to-date
  • [ ] Comprehensive tests (if applicable) have been generated and all pass.
  • [x] The pull request describes the changes that have been made, and enough information is present in the description for any developer to understand what has changed
  • [ ] Commits have been squashed (or will be on merge).
  • [ ] The branch name is descriptive and follows the pull request title format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
  • [x] The pull request title is of the following format : {issue/bug...}/(Issue Number) - Name of issue. E.g bug/30-Fix-Project
  • [x] The description uses github syntax to link to the issue. E,g Resolves se701g2/Doto#{Number}
  • [x] At least two reviewers assigned. One of which must be the assigner of the issue.
  • [ ] If there are merge conflicts, run git rebase as opposed to git merge with master.