chore(deps): Bump PPDS.Dataverse and PPDS.Migration

[dependabot]

Updated PPDS.Dataverse from 1.0.0-beta.3 to 1.0.0-beta.4.

Release notes

Sourced from PPDS.Dataverse's releases.

1.0.0-beta.4

Fixed

• NuGet plugin package deployment now works correctly (#​62)
  • Package ID is read directly from .nuspec inside the nupkg (authoritative source)
  • Dataverse extracts uniquename from package content automatically - CLI no longer sets it
  • Solution association works on both create and update via SolutionUniqueName request parameter
  • Removed unnecessary publisher prefix querying logic
• What-if simulation for new NuGet packages no longer throws an exception

Commits viewable in compare view.

Updated PPDS.Migration from 1.0.0-beta.3 to 1.0.0-beta.5.

Release notes

Sourced from PPDS.Migration's releases.

1.0.0-beta.5

Fixed

• Thread-safety in PluginRegistrationService - Changed entity type code cache to ConcurrentDictionary

Added

• PluginRegistrationConfig.Validate() method with executionOrder range checking (1-999999) - called before plugin deployment

Changed

• Extracted ParseBypassPlugins method to DataCommandGroup to eliminate duplication
• Extracted constants in PluginRegistrationService (ComponentTypePluginAssembly, StagePreValidation, etc.)
• Removed manual Ctrl+C handler - relies on System.CommandLine built-in cancellation

Full Changelog: joshsmithxrm/power-platform-developer-suite@Cli-v1.0.0-beta.4...Cli-v1.0.0-beta.5

1.0.0-beta.4

Fixed

• NuGet plugin package deployment now works correctly (#​62)
  • Package ID is read directly from .nuspec inside the nupkg (authoritative source)
  • Dataverse extracts uniquename from package content automatically - CLI no longer sets it
  • Solution association works on both create and update via SolutionUniqueName request parameter
  • Removed unnecessary publisher prefix querying logic
• What-if simulation for new NuGet packages no longer throws an exception

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: dependencies, nuget. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[joshsmithxrm]

Incorporated into #85

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.