Define Time module release process and versioning conventions

## What

Define and document the release procedure for the `inc_time` module: how to cut a release, how to increment the version in `MODULE.bazel`, and how to verify release readiness before tagging.

## Background

The `inc_time` module currently has no documented release procedure. As the module progresses toward S-CORE v1.0, the team needs a clear, agreed process covering:
- which versioning scheme to use and when to bump major / minor / patch
- what CI gates must be green before a release is tagged
- how to create a GitHub Release and tag
- what to include in release notes / changelog
- API and ABI compatibility expectations between releases
- who must give Committer sign-off and through which GitHub mechanism

## Acceptance criteria

- [ ] A release process document is authored (e.g. `docs/release/release_process.rst` or `RELEASING.md`)
- [ ] The document specifies the versioning scheme (e.g. semantic versioning) and rules for incrementing major / minor / patch
- [ ] The document lists the minimum CI gate requirements that must be green before a release tag is created
- [ ] The document specifies the required approval (Committer sign-off) and the GitHub mechanism (PR review / release draft)
- [ ] The document describes how breaking API changes are handled and communicated
- [ ] The document is reachable from `docs/index.rst` or the repository README