Remove lockfile maintenance from Renovate and wait for `pylock.toml` support

[harryswift01]

Description

Our Renovate configuration currently has lockFileMaintenance enabled, but CodeEntropy does not use lock files yet. With the introduction of PEP 751, Python now has a standardized lockfile format (pylock.toml) designed to ensure dependency reproducibility and deterministic environments.

Renovate does not currently support the pylock.toml format, meaning lockfile maintenance will not function. Instead of adding a lock file prematurely, we should remove lock file maintenance configuration now, and introduce pylock.toml later once Renovate adds support.

This keeps our configuration clean and positions the project for future reproducibility improvements without unusable settings in the meantime.

---

Scope

• Remove lockFileMaintenance from renovate.json
• Keep existing dependency workflow unchanged
• Track Renovate progress for PEP 751 lockfile support
• Introduce pylock.toml when Renovate can maintain it automatically

---

Tasks

• Remove lockFileMaintenance from renovate.json

---

Benefits

• Clarity: Removes configuration for features we cannot yet use
• Reproducibility-ready: We can adopt a standardized lockfile as soon as support lands
• Future-proofing: Aligns the project with Python's evolving packaging ecosystem
• Less noise: Reduces Renovate tasks/PRs that would currently do nothing