Catch all exceptions getting version from VCS, fallback to importlib

[rgoya]

This closes #1960.

anndata developers are using hatch build tool with a hatchling backend and relying on the hatch project configuration to make sure the version is up to date. However, the chosen approach can generate conflicts when the user has a pyproject.toml file of their own (see #1960).

This PR makes sure to catch all exceptions generated while trying to read the dev configuration and fall back to importlib. Additionally, as a safeguard, even if hatchling can parse and provide the data from the pyproject.toml, we will fallback to importlib if the project found does not match the expected project name.

The project name is placed as a private constant so that it can be ported to other scverse tools that need it.

• Closes Latest anndata (v0.11.4) fails to import after trying and failing to get data from pyproject.toml #1960
• Tests added
• Release note added (or unnecessary)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.07%. Comparing base (089ed92) to head (657cc3d).
⚠️ Report is 38 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1972      +/-   ##
==========================================
- Coverage   87.13%   85.07%   -2.07%     
==========================================
  Files          47       47              
  Lines        6848     6852       +4     
==========================================
- Hits         5967     5829     -138     
- Misses        881     1023     +142     

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

... and 7 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[rgoya]

@flying-sheep , a gentle poke on this PR.

You mentioned you were over the versioning thing; however, not being familiar with how your dev/build process looks like, I didn't feel confident removing the hatchling code.

Instead, the code here:

• adds some guardrails to ensure the right data is being accessed (e.g. if pyproject.toml is found, make sure it is anndata's), and
• ensures that if the hatchling related versioning fails for any reason, it fallbacks to importlib (e.g. silently catching known exceptions, and unknown exceptions with a warning).

[flying-sheep]

Hi! Yeah, that looks wonderful and thorough. The decision of keeping or removing the whole thing can happen independently from making it more robust!

Thank you