ATS 1.5 parse pipeline to consider handling open() events recoverably

During one of my own timeline test runs, I've been seeing a stack trace warning that the CRC check failed in Filesystem.open() file; something the FS was ignoring.

Even though its swallowed (and probably not the cause of my test failure), looking at the code in LogInfo.parsePath() that it considers a failure to open a file as unrecoverable.

on some filesystems, this may not be the case, i.e. if its open for writing it may not be available for reading; checksums maybe a similar issue.

Perhaps a failure at open() should be viewed as recoverable while the app is still running?