dotnet automation api ImportStackAsync and ExportStackAsync

[t0yv0]

Could't use Deplomyent as in node SDK as this is taken by something else. So StackDeployment. Good name?

Should I add show-secrets flag?

Do we want ImportOptions and ExportOptions with OnStandardError etc.

[t0yv0]

CC @orionstudt

[t0yv0]

TODO: PR against feature-3.0 to bring in compliance with #6415 that is pass --stack

[t0yv0]

Thanks a ton for the review! I'm converging on shipping is for now as other methods don't have detailed Options yet either. @komalali ready for final review.

[vipentti]

Consider adding the methods to WorkspaceStack so you can do stack.ExportAsync and stack.ImportAsync to match the nodejs api and for convenience when working with a specific stack. E.g. instead of having to do stack.Workspace.ExportStackAsync(stack.Name).

Something like:

/// <summary>
/// Exports the deployment state of the stack.
/// <para/>
/// This can be combined with ImportStackAsync to edit a
/// stack's state (such as recovery from failed deployments).
/// </summary>
public Task<StackDeployment> ExportStackAsync(CancellationToken cancellationToken = default)
    => this.Workspace.ExportStackAsync(this.Name, cancellationToken);

/// <summary>
/// Imports the specified deployment state into a pre-existing stack.
/// <para/>
/// This can be combined with ExportStackAsync to edit a
/// stack's state (such as recovery from failed deployments).
/// </summary>
public Task ImportStackAsync(StackDeployment state, CancellationToken cancellationToken = default)
    => this.Workspace.ImportStackAsync(this.Name, state, cancellationToken);

[t0yv0]

@komalali this should be good to review one last time (need a :stamp) and I can merge.