Prepare configuration packages as inactive and activate them selectively

When a configuration package is copied, its assignment rules are also copied. As a result, the copied checks can already run on devices before the rules and check settings have been adjusted.

Copied packages should therefore remain inactive at first. They should only be applied to the selected devices after they have been explicitly activated. The original package should continue to run unchanged.

In addition, configuration packages should generally be able to be deactivated and reactivated later without losing their rules and settings. The activation status should be clearly visible in the package overview and within the package itself.

This allows even large packages to be prepared without having to create new checks individually or triggering unintended executions and error messages during preparation.

Internal: Issue 2398