Pulsar uses a separate JVM configuration for each component

At present, each component of pulsar uses the configuration of broker JVM, or it has to be set by export, which cannot be solidified. When multiple components are restarted, the original JVM configuration will be lost. So I want each component to use its own JVM configuration file for long-term recording.

No files or tests are named. Start by tracing how broker JVM configuration is supplied to each Pulsar component and how component restarts currently obtain it; define the component-specific configuration entry points before implementation. Done means each component can persist and reload its own JVM configuration across restarts.

Written by the indexing model from the issue text.