Mark intrinsics as safe where possible, or provide safety docs

[Firestar99]

I'm deliberately skipping mod raytracing since the safely specification on those intrinsics is a little more involved, with both ray pipeline and ray query having a quite complex state and UB rules around it.

closes#382

[nazar-pc]

This is very helpful!

Looks like atomic operations like atomic_i_add() are still unsafe, would appreciate similar updates there.

[Firestar99]

Atomics are really difficult to make safe. You can misuse scope to get the value to an undefined state. And I'm unsure how Vulkan, let alone other APIs, handle atomic and non-atomic read/write aliasing.

[nazar-pc]

All the more reasons to add "Safety" section to them. If it is difficult to rust-gpu maintainers, there is no hope for casual GPU developers like myself to use them correctly 😂

On CPU at least atomic operations on integers are perfectly safe, there is no memory unsafety that can be caused by them. I recently opened #399, maybe atomics need to start working with standard library types like AtomicU32 instead of u32 to reduce the confusion?