bug: openshell.spec Version/Release does not follow Fedora conventions #3515

Part of: #3511

User Story

As a Fedora packager, I want openshell.spec's Version/Release fields to follow Fedora's versioning guidelines, so the package can be properly tracked and updated through normal Fedora release/update tooling (Bodhi, etc.).

Problem Statement

The spec is currently pinned to a stale %global openshell_version 0.0.37 (current main is well past 0.0.116), and Release is set to a non-standard, git-describe-style string rather than a conventional Fedora release value.

Impact / Why This Matters

A stale, non-standard version/release scheme blocks Fedora review outright (Fedora's Version/Release guidelines are strictly enforced) and makes it unclear how future version bumps should be handled without breaking Bodhi's update tracking.

Acceptance Criteria

• Version tracks the actual current OpenShell release version
• Release follows a Fedora-conformant scheme (e.g. %autorelease/%autochangelog via rpmautospec)
• A documented process exists for bumping version on new upstream releases

Reproduction Steps

1. Open openshell.spec and compare %global openshell_version against the actual current version in Cargo.toml/recent releases.

Environment

• N/A — spec-file/versioning issue, not runtime