Attempt to select stack then create as fallback

[aq17]

Description

Fixes #11392

If a user does not have write permission (i.e. read-only), attempting to create the stack first will fail before the stack select fallback is triggered. Flip the logic to select first, then create.

7695311 changed it for python auto API already, this PR does the same for TS, Go, C#

Checklist

• I have added tests that prove my fix is effective or that my feature works

• I have run make changelog and committed the changelog/pending/<file> documenting my change

• Yes, there are changes in this PR that warrants bumping the Pulumi Service API version

[pulumi-bot]

Changelog

[uncommitted] (2022-11-18)

Bug Fixes

• [sdk/{dotnet,go,nodejs}] Attempt to select stack then create as fallback on 'createOrSelect'
  #11402

[ringods]

@aq17 can you also reverse it for C# in this PR?

pulumi/sdk/dotnet/Pulumi.Automation/WorkspaceStack.cs

Lines 129 to 139 in 6a74bc1

	WorkspaceStackInitMode.CreateOrSelect => Task.Run(async () =>
	{
	try
	{
	await workspace.CreateStackAsync(name, cancellationToken).ConfigureAwait(false);
	}
	catch (StackAlreadyExistsException)
	{
	await workspace.SelectStackAsync(name, cancellationToken).ConfigureAwait(false);
	}
	}),

[dixler]

Nice. I have 1 suggestion around simplifying the retry logic in Go. (also you have a small lint error)

Addressed

[ringods]

LGTM

[aq17]

bors r+

[bors]

Build succeeded:

• bors-ok