Idea: Release the SecretManagement and SecretStore modules with PowerShell

Summary of the new feature / enhancement

As a user, I have a consistent need to manage secure strings without exposing them in scripts and other automation artifacts. To rely on this capability in PowerShell, I need it to always be available without the need to add the installation to every new project, or finding workarounds to add it in the tools of my choice that run PowerShell.

Proposed technical implementation details (optional)

This experience would align with other modules that are released with the "default" installation footprint of PowerShell. There is no need to merge the source repo's or manage the projects as a single entity. When the PowerShell packages are built, the latest Microsoft.PowerShell.SecretManagement and Microsoft.PowerShell.SecretStore modules would be included.

首先阅读此 RFC 及其包含 28 条评论的讨论，然后追踪 PowerShell 如何定义其默认安装内容范围并组装软件包内容。当社区就将最新的 Microsoft.PowerShell.SecretManagement 和 Microsoft.PowerShell.SecretStore 模块纳入 PowerShell 软件包的路径达成一致时，即表示完成。