Widen omop-alchemy, oa-configurator, and omop-emb pins to semver ranges

[nicoloesch]

• Closes Relax omop-alchemy / oa-configurator / omop-emb pins to semver ranges #32.

Now that #28 put this repo and its upstream packages on label-driven semver, replaces exact pins with >=current,<next-major ranges across all three sibling deps (omop-alchemy, oa-configurator, omop-emb, including the faiss-cpu/pgvector extras). Also aligns the dev extra's oa-configurator[postgres] floor with the main pin, and makes the postgres extra's omop-alchemy[postgres] bound explicit. Verified via uv lock this was already effectively bounded through the main deps entry (PEP 508 resolvers merge multiple requirement lines for the same package), so this is a readability change, not a functional one.

Also installs the cava-devops pre-commit hook so future dependency edits keep uv.lock surgically in sync without relying on memory:

chmod +x .githooks/pre-commit
git config core.hooksPath .githooks

Notes

CI on this PR will fail until cava-devops PR AustralianCancerDataNetwork/cava-devops#2 merges to main

• ci.yml here already points at @main for the --frozen-based build-test.yml, which doesn't exist there yet. This is expected and will resolve on its own once that PR merges; no action needed here beyond waiting.

[nicoloesch]

It was decided to absorb this change by #34 to prevent changing the semver ranges for a second time with the imminent BREAKING releases.