…n. Good time for automated testing

…oes not render

…ause line endings shouldn't matter

Code does not implement saving

Need to persist the change across runs

Let's:
* Add and call code to load and save data
* Add file safe string functions to tasks

Source branch we are merging from spreads out Date parsing too wide

This increases the possiblity for inconsistency

Let's move the parsing of strings to LocalDate into the Deadline class

Currently, the project src files are all in one single src folder.

This makes it very unclear what files are logically together and clutter the folder view.

Let's
* Create a top level package 'duke'
* Create the sub-packages 'command', 'exception' and 'task'
* Leave the files; 'Duke', 'Parser', 'TaskList', 'TaskListFileUtils' and 'Ui' in the top level package 'duke'.

Note that I only place files that will have more than one related file into packages.
I currently do not have any packages with only one file for now.
Whether that is best practice or not is unknown, and may change in the future.

The created object oriented classes is disconnected from the actual Duke main function

There is a requirement for OOP to be used extentively by CS2103T

Let's
* Remove ill-formatted strings due to indiscriminate package refactoring
* Properly flesh out Ui class functionality
* Intergrate prevously created class into Duke
* Edit TaskList and Storage to accomidate each other
* Edit TaskList and Ui to accomidate error printing

Search is currently only a wrapper on contains()

This is bad because this breaks intuition (At least my intuition) about
how searching should be done. For example: "in" should not match "Beating Minecraft"
and "minecraft" should match it, but both of those cases are unfulfilled.

Let's:
* Attempt to check description on a per word basis from the start of the word
** Allow this to be overriden by the presence of multiple spaces
* Do lowercase matching for everything by default
** Allow capital letters in the search to override this.

The reason we allow exceptions is because we sometimes want more specific searching rules.

Added JavaDoc to new functions and made some functions private

…to branch-A-Gradle

Large improvements to code quality

Add one additional assertion for bad code path

Fix at least some of the code quality issues present in branch-A-Assertions

Add assertions and introduce 2 bug fixes

Add Streams and Lambdas

…sages accordingly