Automatic Engagement Numbering (ENG-XXXX)

[PoojasPatel013]

Closes #13592 (Work in Progress)

This PR implements automatic unique ID generation for Engagements. When a new engagement is created, the system assigns a sequential ID (e.g., ENG-0001, ENG-0002) and displays it in the UI.
Changes Implemented

1. Model: Added custom_engagement_id to Engagement model.
2. Logic: Overridden save() method to query the last ID and increment it.
3. UI: Updated view_engagement.html to display the ID next to the header.
   Configuration
   The format can be configured via environment variables or local_settings.py:

• ENG-{id:03d} -> ENG-001
• ENG-{id:04d} -> ENG-0001
• ENG-{id} -> ENG-1
  etc.
  Test Results & Verification

1. Database: Ran makemigrations and migrate successfully.
2. Creation: Successfully created new Engagements without errors.
3. List Views: Verified "Engagement ID" column appears in: Engagements -> All Engagements , Engagements -> Active Engagements, Product -> Engagements Tab
4. Stability: Verified that pages for the Engagement sec load correctly.

Pending Edge Case (Need Feedback)
I am currently debugging behavior related to deleted engagements.

• Current behavior: If I delete the last engagement (e.g., ENG-0005), the query Engagement.objects.last() might behave unexpectedly depending on how DefectDojo handles "Soft Deletes" vs "Hard Deletes."

[Maffooch]

Hi @PoojasPatel013 PR are only accepted against the dev or bugfix branch

[PoojasPatel013]

Hi, This draft PR is not meant to be merged, I needed few feedback from @valentijnscholten and update on progress.