Add bevy_mod_config to Assets/Configuration

[SOF3]

No description provided.

[Copilot]

Pull request overview

Adds a new asset metadata entry for the bevy_mod_config crate under the Assets/Configuration category, consistent with the existing asset listing TOML schema used elsewhere in Assets/.

Changes:

• Added Assets/Configuration/bevy_mod_config.toml with name/description/link/crate metadata.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[alice-i-cecile]

As a potential user, I have a hard time understanding what that means... concretely? Why is it particularly useful for editor UI? What's the relation to persistence? Why would I want a modular configuration framework?

You're welcome to describe your crate however you like: that feedback is merely advisory.

In terms of categorization... maybe something like "settings" would be clearer?

[SOF3]

not sure what is the best way to put it. the idea is that the game developer writes the settings data model, and other plugin providers (those providing a Manager impl) would provide plugins such as persistence and editor UI (and maybe other things you can do with the same data model).
explaining all these would seem too long for a oneline description in the bevy-assets format. what would you suggest about that?

[alice-i-cecile]

My partner says this makes sense to her 😅 I'll just merge this for now; feel free to revise if you have better wording in the future.