Automatically generated actions are packaged, leading to install errors

Problem/Motivation

When a user role is created, actions are generated in the form:

• system.action.user_remove_role_action.[rolename]
• system.action.user_add_role_action.[rolename]

If these actions are added to a feature other than the one that provides the role, an error results when the role is created by a different feature.

Currently, this issue is presenting because of a false positive that assigns all such actions to a 'bundlename_user' feature. That feature then cannot be installed if a feature providing any role is enabled first.

Proposed resolution

Exclude such actions from packaging.

Remaining tasks

User interface changes

API changes

Data model changes