major glam updates break template

Start by inspecting the template dependency declarations and the glam and spirv-std version constraints described in the issue, using PR #12 for context. Reproduce the problem with a fresh lockfile or cargo update, then verify that the generated template compiles without the conflicting glam versions or missing feature configuration.

Noticed a bad precedent while working on https://github.com/Rust-GPU/rust-gpu-template/pull/12:

Whenever glam releases a new major version and you cargo update or generate a new lockfile or generate this template, cargo will choose the most up-to-date glam version for spirv-std. It's declaring >0.30.8, allowing you to use newer glam versions that may have breaking changes, so e.g. 0.32.0 does satisfy this constraint. But the templates specify 0.30.8, which causes cargo to add two glam versions: 0.32.0 for spirv-std and 0.30.10 for the template. Now glam requires that you either enable std or libm (or nostd-libm) as a feature, so the 0.30.10 version will fail to compile, since the template expects spirv-std to do the feature configuration.