A more coherent getting started pathway for Adventure

[kezz]

Right now, users report that there isn't really a clear 'getting started' guide that provides an overview of how to dive into the API.

It would be nice to provide some sort of linear guide, targeting only native platforms, explaining how to:

• Create a component
• Send the component to a user
• Create a component from a configuration using MiniMessage
• maybe some other things?

How much of this can be done in our own docs without making too many assumptions about platforms? How much should be, we link to platforms for their dogumentation instead?

Migrated from https://github.com/KyoriPowered/adventure-docs/issues/150