Simplify vcs version handling

[grst]

One downside of the VCS-based versioning is that when the project
is installed in editable mode, the version encoded in the package
metadata will remain the one from installation time and get stale.

There was some additional code in MuData that attempted to address this,
but I believe it does more harm than good:

• while it would have updated __version__ (which is a convention, but
  not a standard), the standard way to retrieve the version via
  importlib.metadata would still have returned the version number
• It goes hunting for the version number at import time and
  things can go wrong while doing so. In fact, building the conda
  recipe for scirpy fails on CI exactly because some dependency for
  getting the version at runtime is missing
  (https://github.com/scverse/scirpy/actions/runs/21799752388/job/62893203310?pr=672)
  or it might fail because one has a shallow clone without git history
  etc.

With this PR, I propose to get rid of all the additional version
handling and be more aligned with the cookiecutter template. Risking
stale metadata in editable mode is a trade-off that we conciously took
in the template, because the consequences are low-impact and only affect
developers.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.48%. Comparing base (b047610) to head (6b6b416).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #119      +/-   ##
==========================================
- Coverage   68.57%   68.48%   -0.09%     
==========================================
  Files          12       11       -1     
  Lines        1906     1888      -18     
==========================================
- Hits         1307     1293      -14     
+ Misses        599      595       -4     

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

🚀 New features to boost your workflow:

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

[ilia-kats]

I tend to agree generally. The original version of that code was added by @gtca. I'm not sure about the rationale, but I'm assuming the reason is that we're writing the MuData version into the files themselves (we're not reading this currently, but it can help with debugging if you get a mudata file from someone else for example) and it might be a big awkward if you have MuData installed in development mode but also use it productively and share the files with someone else.

But if @gtca doesn't object, I'm inclined to merge this.