[Documentation] Review all cmdlets to include simple output documentation

[msc365admin]

Add a simply .OUTPUTS section specifying the output type, for example:

.OUTPUTS
    PSCustomObject

This keeps the help clean and avoids cluttering it with a full breakdown of all returned properties. I prefer not to include overly detailed documentation inside the comment-based help itself. The .LINKS section points to the official documentation where those details already live, and users can always run the cmdlet directly to inspect the complete output.

Including the output type is helpful because it helps users understand how to process the returned object in scripts and pipelines.

Also align the same simplification for all documentation files, keeping them consistent with this approach.