[ML 0.5/MVI.02.4] Implement LocalDeleteOperationDecider (Domain Logic)

[rafaeltonholo]

Description

Migrate the LocalDeleteOperationDecider from the legacy module (:legacy:core) into a new LocalDeleteOperationDecider interface within the feature domain api :feature:mail:message:list:api and a default implementation inside the :feature:mail:message:list:internal.

Goal

Encapsulate the business rules that determine if a deletion should bypass the trash (e.g., when deleting from Spam/Trash or based on DeletePolicy) without bloating the DeleteMessages orchestrator.

Acceptance Criteria

• Correctly identifies "hard delete" scenarios based on Account settings and Folder type.
• Ensure the logic is tested correctly.

Technical Details

• Need to move both DefaultLocalDeleteOperationDecider(old LocalDeleteOperationDecider) implementation AND tests to the internal feature module
• Need to wire the MessagingController to retrieve the instance of the new interface LocalDeleteOperationDecider via DI.

[mohitsatr]

@rafaeltonholo I want to work on this issue.

The current LocalDeleteOperationDecider is only responsible for handling local messages and does not depend on deletePolicy. The implementations of this new interface should also be only concerned with local messages, right?

e.g., when deleting from Spam/Trash or based on DeletePolicy

I have confusion because of the above line.
thanks