Drop setuptools_scm

It seems that setuptools_scm doesn't work well with pre-commit based
installations where there isn't either a built package or a git
repository to get the version info from.

As well, the version needs to be incremented in the README, so it makes
sense to switch to manually setting the version info.

Author: jonathansick

README.rst

@@ -159,3 +159,24 @@ You can also insert the name of the source docx file using Python format string
            args:
              - "--header"
              - "This file is autogenerated from {docx}. Do not edit."
+
+Development guide
+=================
+
+Release procedure
+-----------------
+
+From the pull request:
+
+1. Update the `changelog <CHANGELOG.rst>`__
+2. Update the version numbers in the ``.pre-commit-config.yaml`` code samples in the README.
+3. Update the version in `setup.cfg <setup.cfg>`__.
+
+Next, merge the PR to the ``main`` branch once checks pass.
+
+Finally, create a Release using the GitHub Release UI from the ``main`` branch. The tag name should be the semantic version set in the first step.
+
+Project information
+===================
+
+pre-commit-docx-plain is developed and maintained by J.Sick Codes Inc.

pyproject.toml

@@ -1,8 +1,7 @@
 [build-system]
 requires = [
     "setuptools>=42",
-    "wheel",
-    "setuptools_scm[toml]>=3.4"
+    "wheel"
 ]
 build-backend = 'setuptools.build_meta'
 

setup.cfg

@@ -29,8 +29,6 @@ package_dir =
     = src
 packages = find:
 python_requires = >=3.7
-setup_requires =
-    setuptools_scm
 install_requires =
     importlib_metadata; python_version < "3.8"
     pypandoc

setup.py

@@ -1,3 +1,3 @@
 from setuptools import setup
 
-setup(use_scm_version=True)
+setup()