Update crate_universe to handle workspace and package resolver definitions

Currently if a package specifies `resolver` there's a risk users could run into the following Cargo error.
```
INFO: Running command line: bazel-bin/wasm_bindgen/3rdparty/crates_vendor.sh '--repin=full'

error: failed to parse manifest at `/tmp/.tmpQivIHn/Cargo.toml`

Caused by:
cannot specify `resolver` field in both `[workspace]` and `[package]`

Error: Failed to update lockfile: exit status: 101
```

crate_universe should be updated to help users avoid this and not require patching out `resolver` in `Cargo.toml` files.