[IMPROVEMENT: BACKEND] Implement catalog soft delete and re-activation logic

[realChakrawarti]

Description

Currently, catalogs are outright deleted after a set time. This ticket proposes a change to this behavior to introduce a 'soft delete' mechanism and a re-activation window, improving data retention and user experience.

Soft Delete Implementation:

• Add a new boolean field active to the Catalog schema, defaulting to true for new catalogs.
• Instead of immediate deletion, when a catalog reaches its inactivity threshold, the active field must be updated to false.
• The updatedAt timestamp of the catalog must be updated whenever the active field is changed to false.

Catalog Re-activation:

• If an inactive catalog (active: false) is accessed/visited by a user within 30 days of its updatedAt timestamp (i.e., 30 days since it was marked inactive), the active field must be reset to true.
• The updatedAt timestamp of the catalog must be updated whenever the active field is changed back to true.

Permanent Deletion:

-[ ] Catalogs that have been marked active: false and whose updatedAt timestamp is older than 30 days must be permanently deleted from the system. This deletion should be handled by a scheduled job or similar mechanism.