Purely formatting (PSR-1/PSR-2). 99% whitespace. Renames GetID->getId

Some resources for best practices and formatting (PHP Specific)
- General Coding Guidelines: http://www.php-fig.org/psr/psr-2/ (also http://www.php-fig.org/psr/psr-1/)
- This one is more about structure/naming than formatting: http://www.php-fig.org/psr/psr-4/

For a more sensible `git diff` try `git diff -w`. This will exclude whitespace changes from the diff.
You can accomplish the same thing on GitHub by appending `?w=1` to the URL.
Adds $hardcoded_tasks (PHP) and simple iteration to display them.

- Uses the exact structure/template that the Javascript is using for "append/create"
- Also adds comment to indicate where tasks will be appended via Javascript

... hey my Tasks added via Javascript are persisting! :confetti:

TODO
- Some thoughts on \Task::__construct (for future refactor)
  - The "id" field should not be required. This should be enforced/determined by the persistance layer and
    the creator of the object shouldn't need to know the state of the current "incrementing id".
  - The "complete" field should be optional and set to "false".
    Or omitted entirely, leaving it up to the creator/consumer to "complete" the Task as needed
Task - Implements JsonSerializable. Adds "fillable" overrides __set.

What is this JsonSerializable wizardy you speak of?!

- See: http://php.net/manual/en/jsonserializable.jsonserialize.php
- Short version: Allows you to explicitly declare what data to serialize when an object is `json_encode`ed
- Also good to know: http://php.net/manual/en/spl.interfaces.php

__set wizardy?
- See method. Super simple.
- Overrides PHP `__set` method which basically allows us to intercept "setting" of properties that we do not want "settable"
Task - Adds toArray(). Refactors jsonSer[...] -($protected_properties)