Lsseq

Using better time-stamp format for specifying the cutoff date for listing sequences
(before or since the date) with --onlyShow. The date format is now:
[CC]YYMMDD[-hh[mm[ss]]] - which gives more terse options for
specifying the date than before, plus it is easier to read.

The older syntax for specifying the date is still quietly supported, but no
longer listed in the help output.

Also fixed two minor bugs with how the --onlyShow feature was working.
1) When using --onlyShow, it was incorrectly listing shots in reverse alphabetical order.
2) The cutoff time was supposed to INCLUDE files up-to-and-including (or including-and-after) the
date specified, but the test was omitting sequences whose times matched exactly instead of including them.

Added the following file types to the default lists of files types considered to be images, or movies or cached sequences.

LSSEQ_IMAGE_EXTENSION
ari - Arri
arw - Sony/Minolta
cr2 - Canon RAW 2
crw - Canon RAW
dng - Digital Negative
orf - Olympus
pef - Pentax RAW
ptx - Pentax RAW 2
raf - Fuji
rdc - Ricoh
rmf - Canon Raw Media Format

LSSEQ_MOV_EXTENSION
mxf - Arri

LSSEQ_CACHE_EXTENSION
tx - Render Texture cached image (eg. Arnold)

Changed code to use PROG_NAME='lsseq' string global variable
which replaces use of sys.argv[0] since the latter does not behave well in all
circumstances. For example under wiz or rez version control systems sys.argv[0]
results in the program name printing as "\_\_main__.py" for usage and error msgs.
Simply using the string 'lsseq' is probably the best solution to this issue.
All regression tests passed - NO change to test-output besides version number
being incremented.

Added three new types to internal default list of image extensions.

File extensions are all matched against image, cache and movie file extensions regardless of case (i.e., uppercase vs lowercase).

Note however, if there is a directory containing a sequence with a mixture of upper and lowercase extensions (for the same sequence that is) - then lsseq will report them as separate sequences. This is likely helpful as it's highly unlikely that anyone intended to mix case between files in the same sequence and probably something is amiss.

For example:

a.1.jpg, a.2.jpg, a.3.jpg a.4.JPG, a.5.JPG, a.6.JPG

will be listed as a.[1-3].jpg and a.[4-6].JPG

This release fixes warnings that weren't printing the filenames with their appropriate paths prefixed (to match actual output of sequence listings). Now warnings for files match prefixes of the native output of lsseq. Eg -p or -P or lsseq dir1/dir2/*.jpg shows the right thing in any warning message. Note that warnings rarely occur with lsseq, only when there are duplicated frame numbers for a given sequence (only possible with different padding) or if there is a broken soft link.

Also, now lsseq always reports broken soft links, no longer reliant on whether or not we're listing error frames. Still silenced with --silent or --quiet.