Implement issue# 12886: function for parsing RFC822/5322 date-time format.

The RFC 822 / 5322 date-time format should be taken out and shot, but
unfortunately, it _is_ used in e-mail, HTTP, RTSP, etc. Most code which
deals with it is probably going to need to handle the rest of whatever
spec it's interacting with rather than just the date-time format, but
there are cases where this would be useful on its own (e.g. Martin
apparently needs something like this in the dmd installer), so I'm
adding a function to parse this format and return a SysTime to
std.datetime.

However, that's all I'm adding. I find it very hard to believe that
anyone who needs to produce this particular format doesn't need a lot of
other functionality specific to whatever spec they're dealing with, and
the function for generating the date-time format presumably will be
included with that (and I definitely don't want to encourage this
format's use anyway, since it's a horrible format). So, I'm just adding
a function for parsing the format, not generating it.

parseRFC822DateTime _should_ fully and correctly implement the format as
outlined in RFC 5322 (including the obsolete syntax from RFC 822 that no
one is supposed to be generating anymore and the comment folding
whitespace nonsense that should never have been legal anywhere but at
the end). And the tests are quite thorough, so it's unlikely that I
missed anything, but you never know.
There are functions for skipping whitespace in general but not just those characters specifically. And since this whole function is index-based rather than using `popFront`, most of the existing algorithms don't work anyway. I could do something like use `find` and check the length of the result to see where the index should be, but that would just be more expensive and wouldn't be much shorter anyway. The only thing that might make sense would be to add a nested function which did specifically what was needed here, but that wouldn't save much code, because there are only two instances of this which are actually the same. This code was written the way that it was to avoid any unnecessary comparisons or other operations, and while there might be a way to make it slightly less verbose, it would almost certainly result in some extraneous comparisons of characters or additional checks for whether the end of the range had been hit.