Port ECS deploy command from SPF

[sathvikkumar-octo]

ECS deploy SPF step replacement in Calamari

Ref MD-1813

• A new Calamari command that wires up CFN deploy + ECS-specific input handling, default tag merging, and output variables matching the SPF contract.
• A default stack-name generator (cf-ecs-{cluster}-{service}-{env}-{tenant}) used when the user doesn't supply one.
• A 1:1 port of lodash's camelCase so Calamari and SPF produce byte-for-byte identical default stack names so that migrating from SPF to Calamari execution doesn't cause new CFN stacks to be created

CFN convention tweaks

• Optional waitTimeout on the wait-for-stack helper; throws on elapse.
• Drops an unused roleArnProvider parameter from the CFN convention constructor.

[Jtango18]

God have mercy on our souls!

Let's mark this class as [Deprecated] from the get go so there's a persistent reminder to replace it.

@zentron Flagging that we need to chat about this

[Jtango18]

🚩 This is passed down to the template and attached to the Stack. or am I missing something here?

[sathvikkumar-octo]

Hmm it seemed unused to me in the convention.

Regardless I'll pull it out into a separate PR

[Jtango18]

public override CreateStackRequest BuildCreateStackRequest()
{
    return new CreateStackRequest
    {
        StackName = stackName,
        TemplateBody = Content,
        Parameters = Inputs.ToList(),
        Capabilities = capabilities,
        DisableRollback = disableRollback,
        RoleARN = roleArn,
        Tags = tags
    };
}

public override UpdateStackRequest BuildUpdateStackRequest()
{
    return new UpdateStackRequest
    {
        StackName = stackName,
        TemplateBody = Content,
        Parameters = Inputs.ToList(),
        Capabilities = capabilities,
        RoleARN = roleArn,
        Tags = tags
    };
}

public override async Task<CreateChangeSetRequest> BuildChangesetRequest()
{
    return new CreateChangeSetRequest
    {
        StackName = stack.Value,
        TemplateBody = Content,
        Parameters = Inputs.ToList(),
        /*
         * The change set name might be passed down directly, or this variable may be
         * set as part of the deployment. Reading the value from the variables here
         * allows us to catch any deferred construction of the change stack name.
         */
        ChangeSetName = variables[AwsSpecialVariables.CloudFormation.Changesets.Name],
        ChangeSetType = await GetStackStatus() == StackStatus.DoesNotExist ? ChangeSetType.CREATE : ChangeSetType.UPDATE,
        Capabilities = capabilities,
        RoleARN = roleArn,
        Tags = tags
    };
}

It is passed to the SDK Request classes

[Jtango18]

nit: While this appears to make sense in the S3 case (vs. Below). Let's pull this out and do it as it's own little PR

[Jtango18]

Looks good. A few minor nits and concern about breaking existing functionality.