Get Monday's date from the current week using the When library (which
provides natural language date parsing, making it super easy to get a
time object for Monday). Then when creating the `TimeEntry`ies for the
generator, fill in Monday–Friday's dates in the output.

A function to generate a weekly time sheet.

Add a new `defaults` key to the config.yml file. Looks like this:

    defaults:
      client:
      project:
      module:
      task:
      work_type:
      time:
      billable:

This will be used to fill in default values when a timesheet is
generated.

The date is allowed to be empty in the config defaults hash. Don't error
if it is.

These tell the Time Task form endpoint that we're submitting a
multiple-time submission request.

Because `strings.Itoa` is so much easier to call than
`strconv.ParseUint`, and I needed to parse ints into strings to build
the URL params in `buildSubmissionParams`
(17f4ecc63615e3f3bef21a80f15e7c7b0e0cffa1).

Function that takes a list of `TimeEntry`ies and builds the necessary
URL params for submission to the Time Task form endpoint.

Not relevant. See 89f766854443a6f7ae20c330547083fd0e075ba9.

We want to be able to get Client, Project, etc. objects given their
name. These functions will look through the fields or objects containing
a list of the thing looked for and return if if its name matches the
search string.

Originally had the idea to generalise the body of the function, but had
trouble making the types generic. Still on the table for later if we
want to deduplicate the code. For now I'm leaving in the repetition
because it works and I don't care with this project.

Embedding this struct prevented us from correctly unmarshalling data
into them. This is because they need to be created like:

    Client{IDName{ID: , Name: ,}}

The fields can't be added in directly.

Save ourselves the headache and just manually repeat the fields. So that
importing works right.

Forgot to add this field originally. Do the same as when we added the
`Time` field.