Fix Via's requirements files

This is the result of running `make --always-make requirements` on
Linux. This fixes a couple of issues that were added to the requirements
files by #905:

1. #905 added a macOS-specific
   dependency ([appnope](https://pypi.org/project/appnope/)) to Via's
   `dev.txt`.

   This happened because the requirements files had been compiled on
   macOS for #905. Requirements
   files have to be compiled on Linux!

2. #905 removed the
   `--allow-unsafe` argument from the `pip-compile` command. This option
   should be used, see: https://github.com/jazzband/pip-tools#deprecations

requirements/build.txt

@@ -2,7 +2,7 @@
 # This file is autogenerated by pip-compile with Python 3.8
 # by the following command:
 #
-#    pip-compile requirements/build.in
+#    pip-compile --allow-unsafe requirements/build.in
 #
 build==0.8.0
     # via pip-tools
@@ -34,5 +34,7 @@ zipp==3.8.1
     # via importlib-metadata
 
 # The following packages are considered to be unsafe in a requirements file:
-# pip
-# setuptools
+pip==23.1.2
+    # via pip-tools
+setuptools==67.8.0
+    # via pip-tools

requirements/checkformatting.txt

@@ -2,7 +2,7 @@
 # This file is autogenerated by pip-compile with Python 3.8
 # by the following command:
 #
-#    pip-compile requirements/checkformatting.in
+#    pip-compile --allow-unsafe requirements/checkformatting.in
 #
 black==23.3.0
     # via -r requirements/checkformatting.in
@@ -46,5 +46,7 @@ zipp==3.8.1
     # via importlib-metadata
 
 # The following packages are considered to be unsafe in a requirements file:
-# pip
-# setuptools
+pip==23.1.2
+    # via pip-tools
+setuptools==67.8.0
+    # via pip-tools

requirements/coverage.txt

@@ -2,7 +2,7 @@
 # This file is autogenerated by pip-compile with Python 3.8
 # by the following command:
 #
-#    pip-compile requirements/coverage.in
+#    pip-compile --allow-unsafe requirements/coverage.in
 #
 build==0.8.0
     # via pip-tools
@@ -34,5 +34,7 @@ zipp==3.8.1
     # via importlib-metadata
 
 # The following packages are considered to be unsafe in a requirements file:
-# pip
-# setuptools
+pip==23.1.2
+    # via pip-tools
+setuptools==67.8.0
+    # via pip-tools

requirements/dev.txt

@@ -4,8 +4,6 @@
 #
 #    pip-compile --allow-unsafe requirements/dev.in
 #
-appnope==0.1.3
-    # via ipython
 asttokens==2.2.1
     # via stack-data
 attrs==20.3.0

requirements/format.txt

@@ -2,7 +2,7 @@
 # This file is autogenerated by pip-compile with Python 3.8
 # by the following command:
 #
-#    pip-compile requirements/format.in
+#    pip-compile --allow-unsafe requirements/format.in
 #
 black==23.3.0
     # via -r requirements/format.in
@@ -46,5 +46,7 @@ zipp==3.8.1
     # via importlib-metadata
 
 # The following packages are considered to be unsafe in a requirements file:
-# pip
-# setuptools
+pip==23.1.2
+    # via pip-tools
+setuptools==67.8.0
+    # via pip-tools

requirements/updatepdfjs.txt

@@ -2,7 +2,7 @@
 # This file is autogenerated by pip-compile with Python 3.8
 # by the following command:
 #
-#    pip-compile requirements/updatepdfjs.in
+#    pip-compile --allow-unsafe requirements/updatepdfjs.in
 #
 build==0.8.0
     # via pip-tools
@@ -36,5 +36,7 @@ zipp==3.4.1
     #   importlib-resources
 
 # The following packages are considered to be unsafe in a requirements file:
-# pip
-# setuptools
+pip==23.1.2
+    # via pip-tools
+setuptools==67.8.0
+    # via pip-tools