Lifetime refactor & crate update

[suprohub]

This PR introduces lifetime annotations and ownership traits to the core component system, improving flexibility and enabling zero-copy deserialization where possible.

Added

• RawTextComponent<'a> generic over the lifetime of borrowed data.
• Optional ownable feature with IntoOwned and ToOwned derives for converting between borrowed and owned variants.
• Optional databake feature for bakeable (const-friendly) component structures.
• Type alias TextComponent = RawTextComponent<'static> preserving the previous API for owned use cases.

Changed

• Renamed TextComponent → RawTextComponent<'a> throughout the entire crate.
• All dependent types (Content, Format, Interactivity, TranslatedMessage, ClickEvent, HoverEvent, NbtSource, Object, ObjectPlayer, PlayerProperties, Resolvable) now carry a lifetime parameter.
• Updated SNBT and NBT parsers to work with the new generic structures.
• Adapted builder traits (Modifier) and BuildTarget / TextResolutor to support lifetime‑aware components.
• Adjusted build.rs translation macro to generate constants compatible with the new API.
• Updated examples, tests, and documentation to reflect the changes.

Fixed

• No runtime overhead for owned components ('static): the new TextComponent alias works exactly as before.
• Resolutors and builders now correctly handle both borrowed and owned data.

Dependencies

• Added ownable, databake as optional dependencies.
• Updated minor version bounds for existing dependencies only as needed.

[DarkMrMelther]

Hello! Thanks for the PR and the patience waiting till the review. The life time refactor seems great, good job, but we should move the MiniMessage integration into another PR, some changes should be made before adding MiniMsg format to the lib, talking specifically of your library, the constructor "minimessage" should be named "from_minimsg" since comes from another format, and should be placed in the minimsg crate, also to avoid having too many empty components we should have a final step that reorders components based on their styles or something similar, also to add the gradient tags we should add first the custom component types, and discuss with 4lve about server-side translations, since they are needed to add gradients for translated texts.

[suprohub]

Hello! Thanks for the PR and the patience waiting till the review. The life time refactor seems great, good job, but we should move the MiniMessage integration into another PR, some changes should be made before adding MiniMsg format to the lib, talking specifically of your library, the constructor "minimessage" should be named "from_minimsg" since comes from another format, and should be placed in the minimsg crate, also to avoid having too many empty components we should have a final step that reorders components based on their styles or something similar, also to add the gradient tags we should add first the custom component types, and discuss with 4lve about server-side translations, since they are needed to add gradients for translated texts.

oka

[DarkMrMelther]

It looks great now! LGTM! I will merge it into a dev branch since it could break Steel if merged into Master