[Time Conductor] Allow real-time timespans beyond 24 hours

[charlesh88]

The Time Conductor only allows real-time timespans up to 24 hours, like this:

23:59:59

However, it should allow an hours input for any arbitrary number of hours up to a limit to be defined by technical limitations. For example:

128:00:00

The UI should be modded so that a variable number of digits is allowed for the hours input, rather than the current hh:mm:ss validation as current. Some examples:

0:04:00
0:40:00
4:00:00
40:00:00
400:00:00

@mudinthewater Thoughts?

[mudinthewater]

Duplicate of #2226 - I'll close it.

[mudinthewater]

I'm fine with this format, but confused - it appears that the catch on newer versions of MCT was added at some point. A while back when I was running it with a default of 10 days, it would work with it, but just wouldn't display the days. It also used to accept input in the form of "d hh:mm:ss" but now appears to block that. You can try the old behavior on the demo site https://openmct-demo.herokuapp.com/#/browse/demo:root/demo:3?view=layout&tc.mode=local&tc.timeSystem=utc&tc.startDelta=1037700000&tc.endDelta=0 and the new behavior on petersmcttest.net. Issue #2226 was asking for the days to be displayed when loaded from index.html, but now it appears that it wouldn't work at all?