Standardize development dependencies

There seems to be a preference towards using `requirements-dev.txt` vs. a `dev` extra for development dependencies, but right now neither `pip install -r requirements-dev.txt` nor `pip install -e ".[dev]" is enough to install all development dependencies.

I’ve added any dependencies listed in the `dev` extra to `requirements-dev.txt` and removed the `dev` extra so that we only have one list of dev dependencies to maintain.

This also pins the `moto` package (used to mock S3 in tests) to version 4.x as version 5 release a few days ago contains breaking changes.

.github/workflows/build.yml

@@ -25,7 +25,6 @@ jobs:
         sudo apt-get -qq update
         sudo apt-get install -y libicu-dev
         make dev
-        pip install -e ".[dev]"
     - name: Run the code format check
       run: make format-check
     - name: Run the linter

Makefile

@@ -8,7 +8,6 @@ build-docker:
 
 install:
 	pip install -q -e .
-	pip install -q twine coverage nose moto boto3
 
 dev:
 	python3 -m pip install --upgrade pip setuptools

requirements-dev.txt

@@ -5,3 +5,6 @@ pytest-env==1.1.3
 pytest-cov==4.1.0
 pytest-mock==3.12.0
 wheel==0.42.0
+twine==4.0.2
+moto==4.2.14
+boto3==1.34.32

setup.py

@@ -44,14 +44,6 @@
             "grpcio >= 1.32.0, <2.0.0",
             "google-cloud-storage >= 1.31.0, < 3.0.0",
         ],
-        "dev": [
-            "twine",
-            "moto",
-            "boto3 >= 1.11.9, <2.0.0",
-            "pytest >= 3.6",
-            "coverage",
-            "pytest-cov",
-        ],
     },
     test_suite="tests",
     entry_points={