Update glam

[XAMPPRocky]

No description provided.

[fu5ha]

Hm, I'm not sure I like the approach of publicly re-exporting glam from spirv_std, especially if we want the separation of concerns discussed in #223. I think this also makes it harder to integrate with macaw to add extensions on top of glam that way. I might go back to the old way in #222 but with the newer glam version

[XAMPPRocky]

I don't have strong opinions, I re-exported from glam because when glam is updated having it as a [crates-io.patch] means that when the version is incompatible cargo will warn that the patch is unused and continue trying to build with the version on crates.io, which I was encountering a lot. Having it as a direct dependency prevents that, and it allows people to use and test the in progress spirv fork of glam without finding a PR on GitHub. Once there's a published version on crates.io I think we can pull it back out.