Timestamp rule matches filenames too broadly, leading to exceptions caused by unparsable timestamps

[kocmana]

Arguments:

-i "IMG_<<TS|yyyyMMdd_HHmmss>>.jpg" -o "<<TS|yyyyMMdd_HHmmss>>.jpg" -p ".\testfiles" -cp

File names matched:

.\testfiles\IMG_20210726_152901.jpg
.\testfiles\IMG_20210726_152902.jpg
.\testfiles\IMG_20210726_152902__01.jpg
.\testfiles\IMG_20210726_152909.jpg
.\testfiles\IMG_20210726_154326.jpg
.\testfiles\IMG_20210726_154330.jpg
.\testfiles\IMG_211946.jpg
.\testfiles\IMG_211948.jpg
.\testfiles\IMG_211951.jpg
.\testfiles\IMG_211954.jpg

Resulting Exception:

21:19:45:923 a.k.f.s.FileRenameTask [ForkJoinPool.commonPool-worker-1] ERROR - Could not finish task with arguments: CommandLineArguments[path=.\testfiles, recursive=false, inputTemplate=IMG_<<TS|yyyyMMdd_HHmmss>>.jpg, outputTemplate=<<TS|yyyyMMdd_HHmmss>>.jpg, dryRun=false, createCopy=true, collisionResolutionStrategy=FAIL]: Text '211946' could not be parsed at index 6

[kocmana]

https://stackoverflow.com/questions/6928267/converting-simpledateformat-date-format-to-regular-expression leaves little hope for an elegant solution, together with limited exposure of DTF generation internals - settling for a MVP solution for now.