chore: fix ci config

[gadomski]

Couple of issues:

• Looks like depedabot was bombing out on the /python directory: https://github.com/developmentseed/cql2-rs/actions/runs/20016782884/job/57395941030. I'm not sure, but my guess is that it was only checking out the directory it was pointed at, which includes a reference to another (non-root) directory. My hope is that by using the directories key, that error will go away
• The CI was using a old version of wasm-pack: https://github.com/developmentseed/cql2-rs/actions/runs/20026458300/job/57424863422#step:4:9 (I have v0.13 on my local, CI was on v0.9). This updates to just use cargo install rather than a (old) custom action.

[kylebarron]

cargo install will take a little while to build from source; ideally you would cache it but idk how hard that is to do

[gadomski]

cargo install will take a little while to build from source; ideally you would cache it but idk how hard that is to do

I think the Rust cache action will get it for us, but this repo really shouldn't be that high-velocity so a bit of a extra time doesn't bother me a whole bunch...

[alukach]

Seems reasonable.

Strangely, the cache DOES seem to work for wasm-nodejs but not for wasm-web. No idea why.