release: v3.3.0 — execution.parallel fix (#35) + pom.xml url

[shossain786]

Summary

Debt-retirement release, not a distribution push. Ships exactly what is already on master — nothing new joins it.

• The behaviour change from docs: parallel.md advertises unsupported "tests" mode; ExecutionValidator rejects it with a misleading error #35 (execution.parallel validated against TestNG's own modes — tests and instances are now accepted, matching none/methods/classes) has sat on master since PRs docs: remove false "parallel: tests" claim from docs (fixes #35) #36/fix: validate execution.parallel against TestNG's own modes (#35) #37 (Jul 28) with no user-visible release recorded anywhere. This bump surfaces it.
• Version bump 3.2.0 -> 3.3.0 across every file the release checklist in CLAUDE.md names, plus one additional live snippet caught by grep (docs-site/docs/migration/from-selenium-testng.md).
• Dropped the "accepted from the next release onwards" gating note for tests/instances in docs-site/docs/configuration.md and docs-site/docs/guides/parallel.md — 3.3.0 is that release.
• pom.xml top-level <url> changed from https://github.com/seleniumboot/selenium-boot to https://seleniumboot.com — this is the reason to ship: Maven Central, MvnRepository, Libraries.io, and Sonatype all read this field and currently advertise GitHub instead of the marketing site. <scm>, <licenses>, and <developers> URLs are untouched.

Not included (out of scope for this release)

• No feature work, no dependency bumps, no unrelated docs fixes.
• docs-site/docs/cloud-execution.md's "Requires Selenium Boot 3.2.1+" gate is untouched — that's a different, not-yet-shipped feature, unrelated to docs: parallel.md advertises unsupported "tests" mode; ExecutionValidator rejects it with a misleading error #35.
• PLAN.md is listed in the CLAUDE.md version-bump table but does not exist in this repo — nothing to update there.
• Website LATEST_VERSION (separate repo) is intentionally not touched here — that's a post-Central-publish follow-up per the release checklist.

Test plan

• mvn clean verify — BUILD SUCCESS, 494 tests, 0 failures, 0 errors.
• grep -rn "3.2.0" across tracked files — remaining hits are historical CHANGELOG entries and an unrelated issue-template placeholder, left as-is.
• Verified only the top-level project <url> changed in pom.xml (<scm>/<licenses>/<developers> diffed clean).

Explicitly not done here (needs maintainer go-ahead)

• No tag pushed, no GitHub Release created, no mvn deploy to Maven Central — per the release checklist these come after this PR merges, and Central publish is a manual, irreversible maintainer step.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com