Default behavior of nickel-lang-core's build script burns 100% CPU for minutes

[cbiffle]

Describe the bug
If you are (say) attempting to try out Nickel by adding nickel-lang-core to a project, your next build will not go well.

To Reproduce

cargo new nickeltest
cd nickeltest
cargo add nickel-lang-core
cargo build

This will burn at least one core at 100% for at least minutes (I wound up killing it). GDB attached to the build script shows it's off doing something in lalrpop.

I notice that your workspace has opt overrides for lalrpop in the top-level Cargo.toml; these won't apply to anyone trying to use your package, and it may be worth figuring out a way to avoid needing them. I wonder if there's a way to check in the results of whatever it is lalrpop is doing.

Adding a profile override to my package's Cargo.toml "fixes" this problem, but I'm attempting to write a library crate, and I can't expect all of my downstream users to do that.

Expected behavior
The build completes without taking 100% CPU for minutes on end without making apparent progress.

Environment
Linux.
rustc 1.82.0 (f6e511eec 2024-10-15)

nickel-lang-core 0.10