🧹 Clarify and Align Tagging Policy Across rust-base-containers

### 📝 Description

Our current tag history includes a mix of:

* `v0.X.Y` tags (e.g. `v0.1.3`, `v0.1.4`) for repo-level container releases
* `v1.83.0`, `v1.83.1` tags that ambiguously overlap with the Rust toolchain version but do **not** reflect semantic versioning of this repository
* No version bump to `rust-runtime:0.1.3` in recent commits, yet a `v0.1.4` tag was pushed

This creates potential confusion around which tags apply to `rust-dev`, `rust-runtime`, or both.

---

### 🧭 Proposed Fixes

* ✅ **Affirm `v0.X.Y` as the canonical release tag format for this repo**

* These tags indicate meaningful changes to CI logic, container definitions, or image behavior
* 🔁 **Avoid tagging based on Rust version (e.g. `v1.83.0`) unless justifiable**

* Prefer tagging images as `rust-dev:1.83.0-revN`
* 📝 **Clarify in `CONTRIBUTING.md`:**

* That `rust-runtime` only bumps when downstream crate versions change
* That Git tags (e.g. `v0.1.4`) apply to **this repo**, not necessarily both images
* 🧹 **Audit or delete old `v1.83.x` tags** if they're inconsistent with current policy

---

### 📋 Metadata

```markdown
| Field | Value |
|--------------|--------------------------------|
| Status | Ready |
| Type | Task |
| Area | CI / Release Process |
| Priority | Medium |
| Blocked By | N/A |
| Branch | TBD |
```