Revert numerical stability hotfix

[maresb]

This reverts commit 3edaae2.

This will be safe once celeri requires a release of PyMC where pymc-devs/pymc#7996 has been merged.

TODO: increase the required PyMC version accordingly once a suitable release has been made.

[github-actions]

Hi @maresb,

main has updated pixi.lock since this branch was last synced. Merge or rebase the latest main so dependency metadata stays current.

Remote upstream should point at brendanjmeade/celeri; your fork is maresb/celeri.

git checkout revert-hotfix
git fetch upstream
git merge upstream/main

If merge conflicts occur in pixi.lock, accept the incoming changes from main, regenerate the lockfile, then continue the merge once everything is staged:

git checkout --theirs pixi.lock
pixi lock
git add pixi.lock
git merge --continue

This reminder will be minimized automatically once pixi.lock matches main.

---

Generated automatically by .github/workflows/lockfile-alert.yaml.

[maresb]

pymc-devs/pymc#7996 has been merged to main, so the next release after the current one (v5.27.0) should work.

[maresb]

I verified that the latest PyMC solves the issue when the hotfix is reverted, via the procedure of #341 (comment).

The PyMC version constraint has been updated. Until the release occurs, this defines an unsolvable environment.

TODO: lock and merge once the release comes out.