Dynamic library version from package

Why these changes are being introduced:

Formerly, the python library version number was set via the
pyproject.toml file.  This worked, as the actual package itself
could provide the version by reading the installed package
metadata.  However, some best practices discourage this, as it
relies on the packing and metadata reading.

We may choose to revisit this approach as we get farther along,
particularly if installing via a Github tag or release is
important.

How this addresses that need:
* Version is set in timdex_dataset_api.__init__.__version__,
allowing it to be read directly from the library
* Packaging via pyproject.toml uses this version number via a
"dynamic" metadata field

Side effects of this change:
* None at this time

Relevant ticket(s):
* https://mitlibraries.atlassian.net/browse/TIMX-414

Author: ghukill

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "timdex_dataset_api"
-version = "0.1.0"
+dynamic = ["version"]
 description = "Python library for interacting with a TIMDEX parquet dataset"
 readme = "README.md"
 requires-python = ">=3.12"
@@ -116,3 +116,6 @@ max-doc-length = 90
 
 [tool.ruff.lint.pydocstyle]
 convention = "google"
+
+[tool.setuptools.dynamic]
+version = {attr = "timdex_dataset_api.__version__"}

timdex_dataset_api/__init__.py

@@ -1,8 +1,3 @@
 """timdex_dataset_api/__init__.py"""
 
-from importlib.metadata import PackageNotFoundError, version
-
-try:
-    __version__ = version("timdex_dataset_api")
-except PackageNotFoundError:
-    __version__ = "unknown"
+__version__ = "0.1.0"