AB#139711: Small improvements of the draft feature

[Joselgc1]

Description

Improves the draft-record workflow.

This change:

• Reduces the draft autosave delay to five seconds after the latest edit.
• Displays a timestamped autosave confirmation with seconds.
• Adds Creation Date and Last Updated columns to the draft list.
• Adds backend pagination and sorting for both timestamp columns.
• Loads only draft IDs and timestamps when listing drafts.
• Loads full record data only when a draft is previewed or selected.
• Displays a snackbar after successfully loading a draft.
• Handles stale requests, deletion failures, and autosave race conditions.

Useful links

• https://dev.azure.com/WHOHQ/EMSSAFE/_workitems/edit/139711/

Type of change

• Improvement (refactor or addition to existing functionality)

How Has This Been Tested?

• Created and automatically saved draft records from the record creation modal.
• Verified autosave occurs five seconds after the latest edit.
• Verified the autosave confirmation displays the date, time, and seconds.
• Verified Creation Date and Last Updated display seconds.
• Verified backend pagination and sorting on both timestamp columns.
• Verified previewing and loading drafts fetches the complete record on demand.
• Verified the successful-load snackbar.
• Verified draft deletion and page refresh behavior.
• Verified submitted drafts become regular records.
• Ran backend lint, TypeScript build, and focused resolver tests.
• Ran frontend shared lint, unit tests, translation checks, and the azure-dev build.

Commands used:

Backend

npm run build
npm run test -- --runInBand __tests__/unit-tests/schema/query/draftRecords.query.spec.ts

Frontend

npx nx test shared --configuration=ci --runInBand
npm run check-i18n
NODE_OPTIONS="--max-old-space-size=8192" \
  npx nx run front-office:build:azure-dev --output-style=static

Screenshots

Automatic updating of new draft records:

Draft record selection:

After loading a draft record:

Previewing a draft record:

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• x ] Any dependent changes have been merged and published in downstream modules