Improve restart and configuration reload flexibility for system operations

Admins want more flexible system operations to restart services and reload configurations or modules selectively, so smaller changes can be applied with less downtime and lower deployment effort. Problem / Pain: During development and deployment, users frequently need to restart the system or reload configuration even when only small, isolated changes have been made. This leads to unnecessary downtime and slows down iteration cycles. In some cases, only specific modules or code-level changes are affected, but the full restart or full configuration reload is still required. Impact / Benefit: More granular control over restart and configuration reload behavior would reduce downtime and improve efficiency in development and deployment workflows. It would also make iterative development faster by avoiding unnecessary full system restarts when only specific parts of the system are affected. Example use case: A user applies changes to a specific module or code area and restarts only the affected part of the system or reloads only selected modules instead of restarting the entire system. Idea source: Customer feedback Vote for this idea if this need is relevant to you as well.