feat: Bumping Pipelines CLI to v0.15.1

[yhakbar]

This pulls in changes that are significant, but not breaking.

First, it adds the ability to leverage the new Pipelines Configuration system to declare configurations for Pipelines workflows. This is new functionality that will receive official documentation here. Note that as of this release, the documentation is still in progress, but the functionality is being dark launched to confirm that it works as expected before making an official announcement.

Second, note that the EnvCommonChanged job has changed in behavior. Pipelines Orchestrate will no longer emit a single job for each AWS account, looking for relevant updates to an _envcommon file that has changed. Instead, a single job will be emitted from the root of the repository that will look for changes throughout the repository. This change leverages the new capabilities released as of v2.0.0 where Terragrunt will dynamically assume the correct role in a given directory through integration with Pipelines.