Fix PowerShell param() ordering in protected-paths.ps1 #4676

Originally written by @Copilot on GitHub.
Imported from https://github.com/ccantynz-alt/Dominat8.com/pull/26

What changed?

• Small fix
• Feature
• Refactor
• Infra / CI

param() must be the first executable statement in a PowerShell script. Set-StrictMode and $ErrorActionPreference preceded it, causing a ParserError on every PR:

ParserError: .github/scripts/protected-paths.ps1:5
   5 |    [string]$BaseRef = "origin/main",
     |                       ~~~~~~~~~~~~~
     | The assignment expression is not valid.

Moved param() above Set-StrictMode / $ErrorActionPreference.

Quality gates (must be green)

• CI build is green
• No unexpected UI/design changes on Dominat8.com
• If protected paths changed: override label OR ALLOW_PROTECTED_PATHS file added with reason

Notes / risks

None — pure statement reorder, no logic change.

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.