Addressed harmless design-bug with output of the --prependPathRel option (complete fix)

The option --prependPathRel should never have printed "./" at the head of any line of output. It's redundant, clutters up the output, and doesn't add any helpful information. However the presence of "./" in a line of output up until this release was totally harmless apart from aesthetic considerations.

Therefor this is a design-bug fix, and with this fix lsseq --recursive --prependPathRel and lsseq --recursive --prependPathRel * (i.e. with the globbing wildcard) NOW produce the exact same results in any given directory from which the above two commands are run.

Stripping "./" from the head of the relative path will not break any scripts that might be using this option, because the path with or without "./" refers to the exact same set of files.

(Note: v3.0.1 missed adding the bugfix for --prepentPathRel to cache and movie sequences, as well as when outputting in a different --format (like nuke, or glob) when using --prepandPathRel. This release fixes that oversight.)