Configuration validation

Pyroscope's configuration includes numerous parameters that depend on each other implicitly. It's entirely possible to misconfigure the setup in a manner where the system operates without explicit errors or failures, yet its behavior becomes unpredictable and challenging to debug.

I propose creating a self-diagnostic routine that analyzes configuration parameters, adjusts default values for dependent parameters accordingly, and alerts users if their configuration is invalid (logically).