Target 0.2.0 development builds on main

[tpn]

Development builds after v0.1.3 currently identify as 0.1.4.dev…, while
main is starting the 0.2.0 development cycle. Use setuptools-scm's built-in
release-branch policy so main, topic branches and detached development builds
produce 0.2.0.dev…. Matching maintenance branches advance patch versions;
exact release and RC tags retain their versions.

The change adds build-based coverage for those checkout states and documents
the policy. The existing 0.1.x branch retains its patch-version configuration.

Validation: versioning and release/package checks pass, including Git-free
source archives and rejection of unsupported tags. Repository hooks pass,
including formatting, mypy and the lockfile check.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• ai-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: NVIDIA/cuPhoton/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b750bfa1-046f-4038-8bc6-ea3715403105

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

_{Comment @coderabbitai help to get the list of available commands.}

[melo-gonzo]

LGTM. Verified main, topic and detached development versions, maintenance-branch patch versions, and unchanged release/RC tag versions. All 75 versioning, package-layout and release tests passed locally. The source archive builds as 0.2.0.dev1+g865b1b1; required CI is green. The existing 0.1.x branch retains its patch-version configuration.