Ab#134566 abc allow outdated files in file fields

[GhaziAlibi]

Description

Implements AB#134566 - Allow outdated files in file(s) fields.

Adds a new option on file questions, "Prevent deleting existing files": users can still upload additional files (within the allowed file number) but can no longer delete files already saved on the record. Instead, saved files can be flagged as "outdated" using a warning icon toggle displayed on each file in the form. The flag can be removed the same way.

Visibility of outdated files is configurable independently in each place files are displayed, so the same record can show them in one widget and hide them in another:

• File question itself ("Show outdated files" option)
• Grid widget (new action "Show outdated files")
• Editor / html widget (new setting "Show outdated files")
• Resources question embedded grid (new property "Show outdated files")

When hidden, outdated files are only excluded from display; they remain part of the stored record value. Outdated files are shown with a warning icon instead of the word "outdated", since users may not understand the term.

Useful links

• Ticket: AB#134566

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Tested manually in back-office & front-office (see video below):

• New options appear on file questions (single & multiple upload) in the form builder
• Deleting / clearing a saved file is blocked with a snackbar; files added in the current session can still be removed
• File limits still respected: single file cannot be replaced, multiple uploads cannot exceed the allowed file number (existing files count)
• Flagging / unflagging a file as outdated in the form, persisted after save
• Outdated files hidden or shown per configuration in: form, grid widget file column, html widget file field, resources question embedded grid
• Two widgets on the same resource with opposite configuration display differently

Screenshots

Screencast_20260720_014929.webm

Checklist:

( * == Mandatory )

( * == 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
• Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145