Using a separately-packaged libwasmtime

Thanks for this tool!

I'd like to package `wasmtime` and (at least initially) `wasmtime-py` on [`conda-forge`](https://conda-forge.org/), a cross-platform, distro-style package ecosystem.

Looking through this package's PEP-517 build system, I see it's:

- downloading and renaming a `.(so|dylib|dll)` at build time
- stashing it in `site-packages`
- discovering via relative paths at runtime

However, I also see more upstream tags of `wasmtime` than PyPI releases of `wasmtime-py`, e.g. at present `39.0.0.1` vs `39.0.0.0`, and the more troublesome historic CVE fix versions.

For a downstream like `conda-forge`, would it be unreasonable/unadvisable to:
- build the `libwasmtime` C API from source
- patch `wasmtime-py` to...
- at build time, skip downloading
- at runtime, look in the Normal Places (e.g. `$PREFIX/lib`) for `libwasmtime.*`
- pin `wasmtimepy` to the major version of `libwasmtime`

Thanks again.