Add Scope to Repositories

Summary of the new feature / enhancement

In order to make repository registration available system-wide we should add a -Scope parameter to Register-PSRepository. This parameter will determine the file path where the repository metadata is stored and therefore determine whether all users can access the repository registration. This change will also introduce the following parameters:

• Add a -Scope Parameter to Register-PSResourceRepository
• Add a -Scope Parameter to Set-PSResourceRepository
• Add a -Scope Parameter to Unregister-PSResourceRepository
• Add a -Scope Parameter to Get-PSResourceRepository
• Add a -RepositoryScope Parameter to Find-PSResource
• Add a -RepositoryScope Parameter to Install-PSResource
• Add a -RepositoryScope Parameter to Update-PSResource
• Add a -RepositoryScope Parameter to Uninstall-PSResource
• Add a -RepositoryScope Parameter to Publish-PSResource
• Add a -RepositoryScope Parameter to Save-PSResource

Proposed technical implementation details (optional)

CurrentUser will remain the default behavior even with these changes.
We will not enforce uniqueness across scope, and therefore need additional parameters to indicate repository scope.

Review the repository-registration entry points named in the issue—Register-PSRepository and the PSResourceRepository cmdlets—then trace how repository metadata paths are selected. Done means all listed Scope and RepositoryScope parameters are covered, CurrentUser remains the default, and registrations can be addressed by scope without requiring cross-scope uniqueness.