Align pytest with score_tooling pin

[Subramanian-K812]

What this PR does

• Adds compile_pip_requirements (BUILD) with a new requirements.txt
  (pytest==9.0.1, pytest-html==4.1.1, pytest-repeat==0.9.4), using
  @score_tooling//python_basics:requirements.txt as a constraint (not a peer
  requirements source), so pytest resolves to whatever score_tooling currently pins.
• Adds requirements.txt.lock — a real, hash-pinned lock generated via
  bazel run //:requirements.update (not hand-written). Currently resolves pytest==9.0.1,
  matching score_tooling@1.1.2's (the version testing_tools itself declares) actual pin.
• Updates .github/workflows/fomat_and_test.yml's test job to install from the lock
  (pip install -e . --no-deps && pip install -r requirements.txt.lock) instead of the
  previously unpinned pip install -e ".[dev]" || true, and adds a
  bazel test //:requirements.test step so a stale lock fails CI loudly instead of
  drifting silently.

Files

File	Change
BUILD	Added compile_pip_requirements; @score_tooling//python_basics:requirements.txt is passed as constraints, not srcs
requirements.txt	New — pytest==9.0.1, pytest-html==4.1.1, pytest-repeat==0.9.4
requirements.txt.lock	New — generated, hash-pinned lock
.github/workflows/fomat_and_test.yml	Test job installs from the lock instead of an unpinned pip install -e ".[dev]"; adds a lock-freshness check (bazel test //:requirements.test)
pyproject.toml	dependencies changed from >= floors to exact pins matching the lock
MODULE.bazel	rules_python bumped 1.4.1 → 1.5.0 — needed for compile_pip_requirements's constraints parameter, added in 1.5.0

Verification

• bazel run //:requirements.update runs clean and produces a valid lock (confirmed
  basedpyright/nodejs-wheel-binaries are absent from the regenerated lock).
• bazel build //... and bazel test //:requirements.test both pass after the
  rules_python bump.
• End-to-end alignment check (done in a throwaway copy, not part of this PR): bumped
  score_tooling to 1.2.0 (pytest unchanged at 9.0.1, consistent) and to 1.3.1
  (pytest 9.0.3 — the merge correctly picked up the new pin after re-running
  requirements.update), confirming the mechanism does what it's meant to.

Known limitations

• Between score_tooling 1.2.0 and 1.3.1 the exported file this PR merges in
  (python_basics:requirements.txt) was renamed to a per-Python-version file
  (requirements_3_12.txt). Bumping score_tooling in testing_tools past that boundary
  will make bazel run //:requirements.update fail to analyze (hard error, not silent
  drift) until the BUILD src is updated to match — noted inline in BUILD's comment.

[PiotrKorkus]

you need to update pyproject.toml thats what is being resolved when we add testing_tools as pip dependency

[PiotrKorkus]

pin the version, otherwise we might end up with failures if it resolves into newer version. This already happened in presistency

[Subramanian-K812]

fixed.

[PiotrKorkus]

    extra_args = [
        "--no-annotate",
    ],

[Subramanian-K812]

fixed.

[PiotrKorkus]

Reduce ai comment

[Subramanian-K812]

fixed.

[PiotrKorkus]

have a single source of reqs to be installed

[Subramanian-K812]

fixed.

[PiotrKorkus]

still two separate installs

[Subramanian-K812]

can't combine into one — pip refuses a local install under hash-checking.

[PiotrKorkus]

you added python toolchain, where is it used?

[Subramanian-K812]

pip.parse hub was not consuming it removed.