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

I was just thinking about that, actually. I was worried that `24` would be incorrectly parsed as `00:00` instead of `02:40`. However, upon a second investigation, that's how the original timepicker parses it, and it's what makes the most logical sense. `23` is also parsed as `23:00` in both timepickers (Which is super weird, because based on our format array, Moment should be using `Hm` to parse that string. In this case, I might be able to cut down that array if you'd like. Because Moment seems to be ignoring some of the formats. Katrina encountered this in her QA, where Moment should have probably read `23:90` as invalid, but instead parsed it as `23:09`.) 
The only other difference between `0+` and `0*` would be the parsing of `24:`, which might as well be parsed as `24:00`, ~~even if that won't work for other times.~~ Apparently, Moment parses `23:` as `23:00`, so using `0*` would definitely align better with Moment actions for other times.