Release 3.2.0

[luigilink]

Pull Request (PR) description

Summary

Adds support for mounting SharePoint content databases in parallel as part of the existing 4-task sequence flow, plus a new InitContentDB Action to generate the source-farm DB inventory. Designed for SP2019 → Subscription Edition migrations. Also removes the unreliable pre-ProductUpdate reboot check.

Changes

• New Mount-SPSContentDatabase function in sps.util.psm1 — validates the target SPWebApplication, skips when the DB is already attached, supports optional -DatabaseServer, logs failures via Add-SPSUpdateEvent.
• New InitContentDB Action in SPSUpdate.ps1 — (re)generates ---ContentDBs.json on the source farm via Initialize-SPSContentDbJsonFile.
• New MountContentDatabase JSON flag — when true, each of the 4 parallel sequence tasks mounts its DB group, then optionally upgrades it. Mount and Upgrade are independent flags (mount-only, upgrade-only, or both are all supported).
• Master and Install branches now spawn the parallel sequence tasks when either UpgradeContentDatabase or MountContentDatabase is enabled.
• Removed blocking Test-SPSPendingReboot call in the ProductUpdate flow — customers observed stale reboot markers (CBS, PendingFileRenameOperations) persisting across multiple reboots, causing false aborts on healthy farms.
• Docs — README, wiki (Configuration.md, Usage.md), CHANGELOG, RELEASE-NOTES updated. Version bumped to 3.2.0.

Task list

• Added an entry to the change log under the Unreleased section of the
  file CHANGELOG.md. Entry should say what was changed and how that
  affects users (if applicable), and reference the issue being resolved
  (if applicable).
• Added/updated documentation and descriptions where appropriate?
• New/changed code adheres to [Style Guidelines]?

[github-actions]

Pester Test Results

87 tests   87 ✅  5s ⏱️
18 suites   0 💤
 1 files     0 ❌

Results for commit cce7e34.

♻️ This comment has been updated with latest results.