Chore(dx): Make py-glaredb crate a more pleasant development experience

[scsmithr]

Description

Currently the dx has been noted as "not great" by a few people on the team.

For me, I'm running into:

• rust-analyzer is "working" but not actually displaying errors in my editor. I can go-to-def or even view function definitions, but I don't get errors to show up. This makes refactoring harder than it needs to be.
• Crates recompiling when they shouldn't be. It seems that running just build will recompile a large number of crates even when changes have only been made to py-glaredb. This, combined with the above, leads long feedback loop. A workaround for this is setting the target dir to something else, like CARGO_TARGET_DIR='./target/ffff' just build.

[universalmind303]

rust-analyzer is "working" but not actually displaying errors in my editor. I can go-to-def or even view function definitions, but I don't get errors to show up. This makes refactoring harder than it needs to be.

I'd love to see if you find a way to get this to work. Every py & js bindings crate i've worked in has had this issue & it drives me nuts.