Pipeline job creation, using the job pattern filter

In !50 (merged), we introduced a CLI argument to update the expectations only for jobs that follow some user-defined patterns in the name. But, the object creation of the collate pipeline requests all the information of the pipeline jobs, no mater if they will later be filtered.

Introducing this argument to the Collate object method to prepare this pipeline object, removes all the unnecessary work, and has a positive impact on the execution time.