Revise Get-TenantPrivateChannelMigrationStatus to adhere to schema

[garycentric]

After PR #13541, the PowerShell build pipeline choked on the content, as identified in Pipelines - Run 2.260504.1 logs.

WARNING: Error encountered: Schema exception. This can occur when there are multiple code blocks in one example.

That actual problem is that the documentation pipeline for Teams uses the old version of PlatyPS, which requires that "Example" sections consist of the following:

### Example title

0 or more parapgraphs
1 or more code blocks
0 or more paragraphs

So, this PR moves the paragraphs that were between code blocks (and one paragraph that was at the end of "Example 3" instead of at the start, where it could describe the content) to the top of their respective sections.

I've also made a blind link explicit by naming the target.

@rohanbharadwaj @ashajoshidu

[learn-build-service-prod]

Learn Build status updates of commit 43159d1:

✅ Validation status: passed

File	Status	Preview URL	Details
teams/teams-ps/MicrosoftTeams/Get-TenantPrivateChannelMigrationStatus.md	✅Succeeded	View (teams-ps)

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 356bfef:

✅ Validation status: passed

File	Status	Preview URL	Details
teams/teams-ps/MicrosoftTeams/Get-TenantPrivateChannelMigrationStatus.md	✅Succeeded	View (teams-ps)

For more details, please refer to the build report.

[github-actions]

@garycentric
You have permissions to sign off pull requests in this repository. Reviewers will not be added to this PR.

Before this PR can be merged, you need to add the Sign off label to it. Before you sign off a PR, confirm the following:

• The PR is not in draft state. When the changes in this PR are ready to be published, select the Ready to merge button at the bottom of the page.
• Article content has been checked for technical accuracy.
• There are no errors or warnings in build validation.
• There are no severity 1 or 2 PoliCheck issues.
• All required PR checks at the bottom of the PR are passing.

After you've confirmed the above, do the following to sign off:

1. Select the gear next to Labels.
2. Select Sign off from the label list.
3. Click away from the label list.

After you've signed off, our operations (PubOps) team will review the PR for issues that may impact formatting and the customer experience. If any changes are needed, they will return
the PR to you with required changes. After they've completed those changes, you need to sign off again.

When the PR passes PubOps review, they'll merge the PR. If the PR is merged into the main branch, changes will go live within the next couple hours.

If you have questions about this process, or need help signing off on this PR, post a message to https://aka.ms/tcphelp.