implement the project.name property, the pipeline does not need to be named based on the config file name.

[IvoryC]

People can run config files that have names like: barrier-fromCounts.config barrier-original.config new-barrier.config barrier-v2.config

And if they are all variants of the "barrier" project, they can all have project.name=barrier and all will create pipelines: barrier_2020Aug20 barrier_2_2020Aug20 barrier_3_2020Aug20 barrier_2020Aug21

If no "project.name" property is found, then pipeline instance generated from barrier-original.config will still be barrier-original_2020Aug20 ; and BioLockJ will set project.name=barrier-original