Fix requirements.lock mismatch in CI

- Regenerated `requirements.lock` using `pip-compile --generate-hashes` to match the format and content expected by the CI environment.
- This resolves the `git diff --exit-code requirements.lock` failure in the `build` workflow.

Co-authored-by: PR0M3TH3AN <[email protected]>

requirements.lock

@@ -1,5 +1,5 @@
 #
-# This file is autogenerated by pip-compile with Python 3.11
+# This file is autogenerated by pip-compile with Python 3.12
 # by the following command:
 #
 #    pip-compile --generate-hashes --output-file=requirements.lock src/requirements.txt
@@ -1473,7 +1473,9 @@ pycryptodome==3.23.0 \
     --hash=sha256:dea827b4d55ee390dc89b2afe5927d4308a8b538ae91d9c6f7a5090f397af1aa \
     --hash=sha256:e3f2d0aaf8080bda0587d58fc9fe4766e012441e2eed4269a77de6aea981c8be \
     --hash=sha256:eb8f24adb74984aa0e5d07a2368ad95276cf38051fe2dc6605cbcf482e04f2a7
-    # via bip-utils
+    # via
+    #   -r src/requirements.txt
+    #   bip-utils
 pydantic==2.11.7 \
     --hash=sha256:d989c3c6cb79469287b1569f7447a17848c998458d49ebe294e975b9baf0f0db \
     --hash=sha256:dde5df002701f6de26248661f6835bbe296a47bf73990135c7d07ce741b9623b