Authentication WIP

[tristanpoland]

This pull request's primary goal is adding authentication features to the community_link_plugin and cleaning up dependencies in Cargo.toml files. Notable changes include adding authentication structures and logic, modifying the PluginConstruct implementation, and updating the Listner struct to handle authentication events.

Authentication Features:

• plugins/community_link_plugin/src/lib.rs: Added AuthCredentials and AuthState structures to handle user authentication data.
• plugins/community_link_plugin/src/lib.rs: Implemented authentication logic, including storing authenticated users and validating credentials.
• plugins/community_link_plugin/src/lib.rs: Modified the Listner struct to handle authentication events and replicate auth state across servers.

Dependency Management:

• backends/stars_beyond/Cargo.toml: Added serde dependency.
• plugins/chronos_plugin/Cargo.toml: Removed auto-generated plugin dependencies.

[tristanpoland]

@Caznix @haywoodspartan @WilliamAnimate Thoughts on handling the player authentication in the link middleware like I have done here? I'm thinking it should be a reasonable way to handle that, but we will need to add a DB URL to the link config JSON file if we go this route.

I had it as it's own plugin but I think its best to keep plugin types that we have a hard dependency on (such as link) to a minimum.

[tristanpoland]

@Caznix Does this look right to you?

[tristanpoland]

This will serve as auth until the horizon_network_api crate is created to replace link plugins.

This Will not be the final auth system and is in no way bullet-proof but merely establishes the beginnings of the API.