Role-based importing permissions and duplicate handling controls

Feature Request: Role-based importing permissions and duplicate handling controls

Summary:
Introduce a dedicated importing permission that controls whether a user can import at all and which duplicate-handling options are available based on their granted permission levels. This ensures administrators can fully govern import access, limit risky actions to authorized users, and hide unavailable options from the user interface.

Problem Statement:
Currently, users with access to importing can perform import actions without enough control over the level of access they should have. This creates two related issues: organizations cannot fully prevent certain users from importing altogether, and they also cannot consistently restrict high-impact duplicate-handling behaviors such as overwriting or replacing all records. As a result, less-privileged or less-experienced users may be able to make bulk data changes that should be reserved for trusted roles, increasing the risk of accidental overwrites, data loss, inconsistency, and time-consuming cleanup.

Proposed Solution:
Introduce a new permission called importing with four permission levels: Access, Add, Edit, and Delete.
Users without Access cannot import at all.
Users with Access only may import using Skip handling only.
Users with Access + Add may import using Skip and Overwrite only.
Users with Access + Add + Edit may import using Skip and Overwrite only.
Users with Access + Add + Edit + Delete may import using Skip, Overwrite, and Replace all.
Any duplicate-handling options the user does not have permission to use should be hidden from the UI rather than shown as disabled.
The system should evaluate the user’s importing permission at the time an import is started and display only the allowed actions.
This permission model should allow administrators to control both whether a user can import at all and the maximum level of impact they can have on existing data during import.
Optionally log the selected duplicate-handling option, along with the user and timestamp, to support auditability and governance.

Benefits:
Prevents unauthorized users from performing imports entirely.
Limits high-impact import behavior to users with the appropriate permission levels.
Reduces the risk of accidental overwrites and destructive bulk updates.
Improves data governance by aligning import capabilities with role-based access control.
Simplifies the user experience by hiding unavailable options and showing only valid actions.
Builds confidence in the import process by enforcing safer defaults and clearer permission boundaries.