fix: forward plugin logging output to Hipcheck core stderr/stdout

[KirilldogU]

Resolves #381.
This PR forwards the logging output of plugins to the stderr/stdout output of Hipcheck core.
It does this through:

• Creating a feature in hipcheck_sdk to initialize an env_logger
• Calling the init_logger() feature from each plugin
• When plugins are launched as a child process, having them inherit the Stderr/Stdout of the parent Hipcheck core process.

It also adds docs in the sdk on how to use the init_logger() feature.

[KirilldogU]

Would appreciate input on:

• Is there a better place than main() for the init_logger() feature to be called in the plugins?
• Is any of the added documentation too wordy or out of place? Specifically, the edit to the rust-sdk.md I am uncertain about as it is not essential to getting started with creating a plugin but it does relate to the features of the SDK.

[j-lanson]

My intuition would be to move the logger initialization into PluginServer::register() if the feature is enabled

[j-lanson]

Currently in the debug output the plugins appear as [2025-02-12T20:43:51Z INFO affiliation]. Would it be possible to have them appear as [2025-02-12T20:43:51Z INFO plugin::affiliation] so that we can control all the plugins' logging at once if we want? (e.g. HC_LOG=plugin=info)

[j-lanson]

Unless init_logger already has idempotency, I might suggest a mechanism like a OnceLock to ensure we only initialize the logger once even if register() happens to be called multiple times (it shouldn't but we don't have a mechanism to prevent someone doing it)