Add steps for using the PowerShell extension for v3 and v4

[TylerLeonhardt]

PR Summary

We've gotten a couple folks struggle to discover that we no longer support v3 and v4 in the PowerShell extension.

Half of the time, they are unable to update to 5.1 or 7... so I've also given them a workaround to use the last version that does support those older versions of PowerShell.

PR Context

Select the type(s) of documents being changed.

Cmdlet reference & about_ topics

• Version 7.x preview content
• Version 7.0 content
• Version 6 content
• Version 5.1 content

Conceptual articles

• Fundamental conceptual articles
• Script sample articles
• DSC articles
• Gallery articles
• JEA articles
• WMF articles
• SDK articles

PR Checklist

• I have read the contributors guide and followed the style and process guidelines
• PR has a meaningful title
• PR is targeted at the staging branch
• All relevant versions updated
• Includes content related to issues and PRs - see Closing issues using keywords.
• This PR is ready to merge and is not Work in Progress
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the
    title and remove the prefix when the PR is ready.

[TylerLeonhardt]

cc @SydneyhSmith @rjmholt

[opbld33]

Docs Build status updates of commit b01e2e1:

✅ Validation status: passed

File	Status	Preview URL	Details
reference/docs-conceptual/components/vscode/media/using-vscode/Install-another-version.png	✅Succeeded	View (powershell-3.0) View (powershell-4.0) View (powershell-5.0) View (powershell-5.1) View (powershell-6) View (powershell-7) View (powershell-7.x)
reference/docs-conceptual/components/vscode/using-vscode.md	✅Succeeded	View (powershell-3.0) View (powershell-4.0) View (powershell-5.0) View (powershell-5.1) View (powershell-6) View (powershell-7) View (powershell-7.x)

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

[SydneyhSmith]

Looks great thanks for adding this @TylerLeonhardt

[sdwheeler]

You say is supports v3 and v4. What about v5.0? That is still out there.

Also, you need to rename the PNG file. It should be all lowercase.

[rjmholt]

What about v5.0? That is still out there.

I didn't think it was; I thought it was a mandatory upgrade to 5.1?

Certainly it's not tested with 5.0 and we haven't seen anyone use it.

[sdwheeler]

What about v5.0? That is still out there.

I didn't think it was; I thought it was a mandatory upgrade to 5.1?

Certainly it's not tested with 5.0 and we haven't seen anyone use it.

OK, I think it is still supported under the Windows Support Lifecycle. But we may have a case for requiring 5.1.

[TylerLeonhardt]

We can add stuff about 5.0 if someone asks - telemetry has shown no usage on 5.0 so we can defer.

[opbld31]

Docs Build status updates of commit 0d2aae5:

✅ Validation status: passed

File	Status	Preview URL	Details
reference/docs-conceptual/components/vscode/media/using-vscode/Install-another-version.png	✅Succeeded	View (powershell-3.0) View (powershell-4.0) View (powershell-5.0) View (powershell-5.1) View (powershell-6) View (powershell-7) View (powershell-7.x)
reference/docs-conceptual/components/vscode/using-vscode.md	✅Succeeded	View (powershell-3.0) View (powershell-4.0) View (powershell-5.0) View (powershell-5.1) View (powershell-6) View (powershell-7) View (powershell-7.x)

For more details, please refer to the build report.

Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.