Bump fallback Version to 0.9.0

[dielduarte]

Summary

• Directory.Build.props still had the fallback <Version> at 0.7.0, two releases behind the latest tag (v0.9.0). Local dotnet build/dotnet pack runs (outside CI) would pick up this stale version since it's not overridden by a tag-derived -p:Version= like cicd/release.sh does for actual releases.
• Bumped it to 0.9.0 to match the latest published release, following the repo's existing convention (see 1173ad5, 0b46e43).

Test plan

• Confirmed no other file in the repo hardcodes the version (only Directory.Build.props)
• release.sh derives version from the git tag via -p:Version=, so this change doesn't affect the release pipeline itself

🤖 Generated with Claude Code

---

Summary by cubic

Aligns the fallback package version with the latest release by updating Directory.Build.props from 0.7.0 to 0.9.0. This ensures local dotnet build/dotnet pack runs use 0.9.0 instead of a stale version when no -p:Version is provided.

• Affects only local or non-tagged builds; the release pipeline still derives the version from the git tag and is unchanged.
• No code or API changes; no migration required.

^{Written for commit 43e4a76. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Auto-approved: Updates the fallback package version in Directory.Build.props from 0.7.0 to 0.9.0 to match the latest release; affects only non-tagged local builds, leaving release pipeline versioning unchanged. No code or behavior change.

Re-trigger cubic</sub>

Approval not submitted

This repository is configured to approve as @klotty, but that approval identity is unavailable.
Reconnect or verify the approval identity in repository settings.

cubic left this as a normal review comment instead of falling back to a Cubic App approval.