Research/perform migration of REST API SDKs to date-based versioning

Community & Support: [LinkedIn Group](https://www.linkedin.com/groups/14656108/) · [Slack #project-nest](https://owasp.slack.com/archives/project-nest)

Active project leaders: Arkadii Yakovets -- [GitHub](https://github.com/arkid15r/) · [LinkedIn](https://www.linkedin.com/in/arkid15r/) · [Slack](https://owasp.slack.com/team/U060W3NKLTF); Kate Golovanova -- [GitHub](https://github.com/kasya/) · [LinkedIn](https://www.linkedin.com/in/kate-golovanova/) · [Slack](https://owasp.slack.com/team/U07PWB1JZ6Z)

[Contributing](https://github.com/owasp/nest/blob/main/CONTRIBUTING.md) · [Code of Conduct](https://github.com/owasp/nest/blob/main/CODE_OF_CONDUCT.md) · [GSoC Mentors](https://github.com/owasp/nest/blob/main/MENTORS.md)

---

**Describe the solution you'd like**

Update the OWASP Nest REST API SDKs to adopt **date-based versioning** instead of semantic versions. This change aims to provide more precise versioning aligned with release dates, while ensuring backward compatibility with existing API prefixes (`v0`, `v1`).

**Proposed change**

* Introduce date-based versioning in SDKs, e.g., `v2026-02-28` / `v2026.02.28` instead of `v0.4.0`.
* Update SDK generation scripts and CI/CD pipelines to produce versioned SDK packages using the new scheme.
* Document the versioning scheme clearly for SDK consumers.

**Expected behavior**

* SDKs with date-based versions should clearly indicate which API release date they correspond to.
* Versioning should be the same for all SDKs we have.

**Acceptance criteria**

* Existing SDKs using `v0` and `v1` continue to function without breaking changes.
* Documentation clearly explains how to select and use a date-based SDK version.

**Are you going to work on implementing this?**

- [ ] Yes
- [x] No