Re-generate code to fix build on ARM Macs

[CyanBlob]

Updating the glam and bevy versions and then re-generating generate.rs fixes #70. This issue seems to ultimately stem from https://github.com/bitshifter/glam-rs/issues/296.

This should be tested on x86 platforms before merging to ensure compatibility wasn't broken.

A better solution will be to eventually generate different code for each platform via cross-compilation.

[makspll]

Hi, yes once aarch64 targets get SIMD support in glam this will disappear, however that seems to require nightly rust to run together with the core-simd feature!

Thanks for the PR!

Changing these signatures does seem to fix this on arm64 however it breaks again on x86, I guess this is the other side of the problem.

A full fix will need to somehow work on both, probably need a bit of logic in the macro code along the lines of:

• According to the expected signature am I generating an A type vector (Vec4A, BVec4A etc) on a platform with no simd support?
• if so before returning, convert using the From trait to an A type vector

However I am not sure this generalizes to all the cases where these vectors are used. Glam is quite confusing, It contains both replacement Vec4 versions for different platforms depending on simd support (the issue we're facing) but also replacement BVec4A and such types which do not use simd instructions on non-simd platforms.

To be honest this seems like a portability issue in glam itself to me. If you rely on an A vector being returned on x86 in your code, this will break on non simd platforms. I think maybe the best fix for now will indeed be generating alternative .rs files depending on simd support, but then removing that once the issue in glam is fixed.

[makspll]

Currently working on trying to generate alternative simd files but cross is playing up: https://github.com/cross-rs/cross/issues/1341

[makspll]

Already fixed on main