Prepare 0.17.0.1 release

[sergey-v9]

Stabilize package versioning and maintainer docs

Summary

• Moves the package family default from 0.17.0-alpha.1 to stable 0.17.0.1.
• Updates Cake and the release workflow so the native engine release is derived from the first three package-version segments (0.17.0.1 -> v0.17.0).
• Replaces the development-era .agents/notes/ files with MAINTAINING.md.
• Refreshes README.md, AGENTS.md, and example package-version defaults to match the stable fourth-segment versioning policy.

Test plan

• dotnet build LadybugDB.slnx -c Release
• dotnet run --project cake/LadybugDB.Build.csproj -- --target Pack --engine-version v0.17.0
• Stale-string search for old alpha/living-notes references

Notes

• This branch was created from the examples branch. If the examples PR has not merged yet, open this PR with base examples/database-usage-samples; otherwise retarget it to main.
• All seven packages should be released with the same 0.17.0.1 version.

[adsharma]

LGTM except for a question about the versioning scheme.

Nuget packages seem to follow semver, which suggests 0.17.0-1 instead of 0.17.0.1. Is this something you considered?

[sergey-v9]

LGTM except for a question about the versioning scheme.

Nuget packages seem to follow semver, which suggests 0.17.0-1 instead of 0.17.0.1. Is this something you considered?

I considered 0.17.0-1, but a hyphen suffix is a prerelease in both SemVer and NuGet. Also considered build metadata (0.17.0+dotnet.1), but NuGet ignores build metadata for package identity. Since the first three numeric segments intentionally mirror the engine's SemVer, I use NuGet's documented fourth Revision segment to represent the binding/package revision.