feat!: use a single BarSettings component

[sparten11740]

Use a single BarSettings component which is more ergonomic to handle.

Closes #27
Closes #18

Migration

-       BarBundle::<Health> {
-           width: BarWidth::new(mesh_width),
-           offset: BarOffset::new(mesh_height),
+       BarSettings::<Health> {
+           width: 5.,
+           offset: 2.,
            ..default()
        },

[sparten11740]

@5tr1k3r is this what you had in mind with a single settings component?

[5tr1k3r]

looks good! I do wonder: why need to use phantom data?

[sparten11740]

why need to use phantom data?

for a generic struct it is necessary to have a field that uses that generic, without phantom data there would be none, resulting in compiler errors such as the following:

Help: consider removing T, referring to it in a field, or using a marker such as std::marker::PhantomData

[sparten11740-bot]

🎉 This PR is included in version 3.0.0 🎉

The release is available on:

• v3.0.0
• GitHub release

Your semantic-release bot 📦🚀