chore!: update atomic dependency

[imrn99]

This required adding a bytemuck::Pod requirements to the CustomFloat trait. Given the description of the trait, the requirement seems reasonable.

[cedricchevalier19]

What is the goal of this bytemuck addition?

[imrn99]

What is the goal of this bytemuck addition?

This is a requirement induced by the new atomic version. From their docs:

This library defines a generic atomic wrapper type Atomic for all T: NoUninit types. Atomic types present operations that,
when used correctly, synchronize updates between threads.

The NoUninit bound is from the bytemuck crate, and indicates that a type has no internal padding bytes. You will need to
derive or implement this trait for all types used with Atomic.