Relax deeplabcut-live pins to >=1.1

[C-Achard]

Context

As mentioned in #38, it may be desirable to avoid pinning the DLC-live version, aside from providing a lower bound.
Each approach comes with its advantages :

• Pinning :
  • Full control over when and what we provide via DLC-live, avoiding potential runtime issues with a newly released latest version
  • Reproducible support + debugging
  • More predictable runtime behavior
• Lower bound only:
  • Users immediately get any improvements and fixes from the latest DLCLive release
  • Less maintenance overhead / versioning PRs
  • Potentially better compatibility in the future
  • ⚠️Less reproducible installls

For the future

• If we go for the lower bound, we could try and provide a "known good" runtime env within the repo to help users install and debugging efforts.
• We may also want to upper-bound it if a 2.0 release with breaking changes ever hits

---

Change strict pins for deeplabcut-live from ==1.1 to >=1.1 in pyproject.toml (base deps, [pytorch] extra, and [tf] extra). This relaxes exact version locking to allow newer releases while keeping 1.1 as the minimum required version.