Publish examples to wgpu.rs on updates to trunk branch instead of gecko

[paul-hansen]

Checklist

• Run cargo clippy.
• Run RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown if applicable.
• Add change to CHANGELOG.md. See simple instructions inside file.

Connections
Fixes #3684

Description
Switched the branch the publish action is using to trunk to allow the examples to be kept up to date as requested in #3684

When testing I ran into the error rustup: command not found in the Main Install Rust WASM target step, I fixed this by using dtolnay/rust-toolchain which is what the Bevy CI template uses for installing Rust in an action. Lmk if you would prefer I revert that.

Testing
I tested this by installing https://github.com/nektos/act and running this command to mimic a github action runner using a minimal image that still contained the Rust stuff needed.

act -P ubuntu-latest=ghcr.io/catthehacker/ubuntu:rust-latest -j publish

Note that it fails at uploading to github pages, which is expected since running locally you wouldn't have access to the secrets needed to do so.

[paul-hansen]

CI failure is not related to this PR. The time crate updated since our last CI run and raised it's MSRV to 1.65 which broke the version of wasm-pack we are using since we compile for 1.64.

[paul-hansen]

Opened a different PR that should fix the CI issue: #3754

[paul-hansen]

Rebased on the latest trunk to get the CI fix

[paul-hansen]

Looks like running the publish job locally is failing due to the updated time dependency too. Working on a fix.

[cwfitzgerald]

We can absolutely run the publishing job on latest stable. Only normal CI needs to check our MSRV

[paul-hansen]

Ah cool, I was thinking of using taiki-e/install-action to install cargo-binstall and use that to install wasm-bindgen-cli. But I was getting a bunch of too many requests errors using binstall so changing it to not use the msrv might be simpler.

[cwfitzgerald]

Thanks so much!