…ing for better clarity (PowerShell#25288)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Co-authored-by: Justin Chung <chungjustin@microsoft.com>

…25359)

…4dae6eaf5e2aa3 to e7a2493ac87dad8aa7a62f079f295e54ff511d88 (PowerShell#25366)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Co-authored-by: Justin Chung <chungjustin@microsoft.com>

Co-authored-by: Justin Chung <chungjustin@microsoft.com>
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>

… PR (PowerShell#25367)

Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>
Co-authored-by: Justin Chung <124807742+jshigetomi@users.noreply.github.com>

…owerShell#25283)

…pper` delegate (PowerShell#25395)

…ical properties for a service (PowerShell#24245)

Co-authored-by: Justin Chung <chungjustin@microsoft.com>
Co-authored-by: Travis Plunk <travis.plunk@microsoft.com>

…25416)

Co-authored-by: Dongbo Wang <dongbow@microsoft.com>

…l#25440)

The WriteImpl() method should always be called within a lock on _instanceLock to ensure thread safety.

…ommand (PowerShell#25437)

…ide default prefix in manifest (PowerShell#20409)" (PowerShell#25462)

…25479)

…erShell#25510)

Co-authored-by: Patrick Meinecke <SeeminglyScience@users.noreply.github.com>

…nState`" (PowerShell#25792)

The change causes nested modules of PSReadLine to be loaded to global session state as well.

It's possible to check if we are currently importing the PSReadLine module but the check would depend on the current design of the PSReadLine module, such as how many nested modules it has, its module type, and etc., which is fragile. It's safer to just revert the change.

…erShell#25108)

Use the help message on the parameter in the completion tool tip to provide better completion help. This can be utilized by other tools to provide more context for a parameter outside of the current type and parameter name which is quite minimal.

…ll#24025)

Always use the v5.1 `$using:` logic when dealing with any connection type that is not based on the `WSManConnectionInfo`. This allows the caller to use the more advanced `$using` features like variables with special names, having `$using` vars inside sub scopes, and more. `WSMan` based connections might still communicate with older versions but as the oldest supported version is v3 on Server 2012. We don't need to keep the default as v2 (which has been deprecated) to support some of the newer features.

…#21188)

…pace is not available (PowerShell#25780)

)

…client and server (PowerShell#25774)