Allow override of the TemplateConfiguration for the CloudFormation provider

When using the ServiceCatalog as a deployment provider you vane the ability to supply a `configuration_file_path`. When you use the `generate_params.py` functionality with a single template in the pipeline you will not have any issues.

But when you have multiple templates that you would like to deploy as part as a single deployment and the CloudFormation Paramaters of those stacks are not equal you will run into issues.

By supporting the `configuration_file_path` for a CloudFormation deployment target you would make it possible to specify specific configurations for these "other" stacks.

A use case for this is combining a delegation role in the master account and the implementation of the service in another account. By keeping them in a single pipeline and repo you make it easy to maintain and the execution order is guaranteed.

Start with generate_params.py and trace how configuration_file_path is handled for ServiceCatalog deployments versus the CloudFormation deployment provider. Verify the behavior for a single pipeline deployment containing multiple templates with different CloudFormation parameters. Done means CloudFormation targets can accept specific configuration files, including the delegation-role and cross-account service case.

Written by the indexing model from the issue text.