Added support for 24:00

## Description and Impact
> Timepicker was able to parse `24:00` when ngModel was changed, but not when the view was changed. This should fix that and add a small test to catch that in the future.

## Deploy Plan
> Does Infrastructure need to know anything special about this deploy? Nope.

## Rollback Plan
* To roll back this change, revert the merge with: `git revert -m 1 MERGE_SHA` and perform another deploy.

## URLs
> [Venue Admin PR](https://github.com/sportngin/venue_admin/pull/116)

## QA Plan
> Review [QA Best Practices](https://source.sportngin.com/page/show/1227795-qa-best-practices).

#### Happy Path Scenarios
> QA has already taken place on Venue Admin

#### Additional Scenarios (Edge Case, Negative, etc.)

#### Regression Scenarios

After reading your comments about parsing, I remembered that I don't think moment's *parser* differentiates between things like `h` and `hh`, I believe the distinction is only relevant for formatting. (though that my be related to the strict parsing option)

I just tested with `var formats = [ 'h:ma', 'H:m', 'hma', 'Hm' ]` and all the existing tests continue to pass.

Do you think the cleanup is worth it?