Implement Image Soft/Hard Delete APIs

[jopemachine]

Motivation

• A new approach to deletion is needed to distinguish between soft delete (setting status to deleted) and hard delete (physically removing the record).
• The existing ForgetImageById might need to be retired or repurposed to align with the new design.

Required Features

• Deprecate or replace ForgetImageById to avoid confusion.
• Introduce a soft delete mutation (e.g., SoftDeleteImageById) that changes the status to deleted.
• Implement a separate purge mutation (e.g., PurgeImageById) that permanently removes the image record from the database.

Impact  

• Existing systems relying on ForgetImageById must either migrate to the new soft delete logic or call purge if they need a permanent removal.
• The database cleanup process now differentiates between soft and hard deletions.

Testing Scenarios  

• Invoke soft delete and verify that the status of the targeted image changes to deleted.
• Attempt operations (e.g., rescan) on deleted images and confirm the expected behavior (e.g., they should be ignored).
• Invoke hard delete (purge) and confirm that the record is fully removed from the database.