Update refs to version number post-release

[github-actions]

automated change, replaces references to the old version number with the new version number upon releases. This PR will need to be closed and reopened to run CI testing.

[singhd789]

Wooo!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.09%. Comparing base (e1177e6) to head (79c669e).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #920   +/-   ##
=======================================
  Coverage   82.09%   82.09%           
=======================================
  Files          67       67           
  Lines        3736     3736           
=======================================
  Hits         3067     3067           
  Misses        669      669           

Flag	Coverage Δ
unittests	82.09% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
fre/__init__.py	100.00% <100.00%> (ø)

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e1177e6...79c669e. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ceblanton]

Hmmm i'm wondering if we should rejigger the steps. The way we have it now, the version references in the docs and in fre --version are inconsistent with the repository tag. (e.g. if you checked out the 2026.01.beta2 tag and built it, fre --version would report the previous tag. The conda package should be right, though, which is more what we care about.