fix: Set Development Status from component_lifecycle (#391)

This automatically sets the Python "Development Status" classifier as
per the [list found here](https://pypi.org/classifiers/) based on the
answer to the "component lifecycle" Copier question.

[From my
understanding](https://packaging.python.org/en/latest/specifications/core-metadata/)
this classifier is not required, just a nice to have. So I'm not too
worried about the potential for a misalignment between the
`component_lifecycle` list of answers resulting in a lack of
`Development Status`, but I am also open to tweaking the template to
always default to "Alpha" status (as it was set to before)

Author: AlexanderWells-diamond

template/pyproject.toml.jinja

@@ -5,8 +5,10 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "{{ distribution_name }}"
 classifiers = [
-    "Development Status :: 3 - Alpha",
-    "License :: OSI Approved :: Apache Software License",
+    {% if component_lifecycle=="experimental" %}"Development Status :: 3 - Alpha",
+    {% elif component_lifecycle=="production" %}"Development Status :: 5 - Production/Stable",
+    {% elif component_lifecycle=="deprecated" %}"Development Status :: 7 - Inactive",
+    {% endif %}"License :: OSI Approved :: Apache Software License",
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",