Adds the raw powershell equivalents for github actions commands

[jessehouwing]

Closes: #15355

Why:

The default shell on Windows ir now pwsh, all of the examples are only for bash. And there are a few caveats.

Ideally the page would be rplit across technology [bash, pwsh, powershell, javascript] and not [linux, mac, windows] cause, like bash, pwsh is also available on all platforms. I couldn't find how to easily make a tech selector for things other than targetPlatform.

What's being changed:

This adds a pwsh example to each place where action command examples are shown in bash.

Staging preview:

• "Workflow commands for GitHub Actions"

Check off the following:

• I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
• For content changes, I have completed the self-review checklist.

Work in progress

• Add some kind of platform / tool selector
• Verify examples for any caveats that may be missing
• Verify the New-Guid approach is valid alternative over getting the sha256 hash of the github token.
• Does there need to be a link to the default shell per platform in here anywhere?

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[ramyaparimi]

@jessehouwing
Thanks so much for opening a PR! I'll get this triaged for review ⚡

[fullofhope336]

``

[jessehouwing]

Some issues with this way of displaying:

For YAML blocks setting the highlighting to powershell the wrong keywords are highlighted.

And it's unclear that this is PowerShel Core 6+ (pwsh) instead of Windows PowerShell 5 and below.

In the legacy example the difference is even more important.

[martin389]

@jessehouwing -- Thanks for the feedback!

For YAML blocks setting the highlighting to powershell the wrong keywords are highlighted.

We don't currently have a way to correctly render multiple languages within the same codeblock 🤔 We're finding that the codeblock titles for "Shell" and "PowerShell" are useful for letting us distinguish them, and saves us from having to keep each example in a separate subsection -- this would occupy a lot more screen space and make it difficult for users to scan through the content.

And it's unclear that this is PowerShel Core 6+ (pwsh) instead of Windows PowerShell 5 and below.

I've added intro text for each of these examples, to make it clearer which version is being referenced. Unfortunately our docs site doesn't let us easily add new languages.

[martin389]

Status update: docs engineering are investigating the staging issue

[jessehouwing]

For some reason this header doesn't render as it's supposed to on the preview environment:

## Echoing command outputs

[martin389]

For some reason this header doesn't render as it's supposed to on the preview environment:

## Echoing command outputs

Looks like your commit fixed it 😄 🎊

[martin389]

Following up on the content plan consideration described here: #15354 (comment)

[martin389]

@martin389 We have an issue that @skedwards88 recently opened to define guidelines for using the tool picker that we should address before adding more tools to it, so that we have a shared understanding for when it's appropriate for the platform overall to include a tool.

Thanks @emilyistoofunky, I've added the reasoning for the two new tools to @skedwards88's issue 👍

[martin389]

This is looking ready to ship 🚢 🎊 Just doing some final checks.

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

[martin389]

@jessehouwing - Thanks again for this great PR, PowerShell users are definitely going to appreciate this update ✨

[martin389]

Changes are now live: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions ⚡