feat(recent-files): allow configuring image grouping

[cristianscheid]

• Resolves: #

Summary

This PR focuses on the backend part of implementation.

• Adds new configurations for Files app:
  • group_recent_files
  • recent_files_group_mime_types
  • recent_files_group_timespan_minutes

Can be set using occ command (examples below):

occ config:app:set files group_recent_files --value=true
occ config:app:set files recent_files_group_mime_types --value='["image/avif","image/gif","image/heic","image/heif","image/jpeg","image/jpg","image/jxl","image/png","image/tiff","image/webp"]'
occ config:app:set files recent_files_group_timespan_minutes --value=5

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[cristianscheid]

/compile

[nfebe]

yolod

[susnux]

Has this been approved by @nextcloud/designers ?

[susnux]

blocking for two reasons:

1. This is completely changing the UI/UX and should go through feature planning / @nextcloud/designers review
2. Have you properly checked virtual scrolling? What happens if you extend them and then scroll down over the scroll order? Because now one item is no longer a fixed height and that can likely break all of the virtual scrolling

[cristianscheid]

Quick update on the state of this PR:

• after reviews raised concerns about the proposed frontend implementation not being mature enough, potentially breaking things, and adding unnecessary complexity, the PR was updated to focus only on the backend portion.
• following feedback from reviews and design team, the settings scope was changed from user level to instance level, configurable only via occ command, as they should not be exposed to end users.

cc @susnux @skjnldsv

[cristianscheid]

@susnux @skjnldsv after some internal discussion we narrowed this PR to focus only on the backend (see previous comment). Would you mind taking another look when you get a chance?

Dismissing this review since the PR now focuses on the backend only and the previous review was about the frontend implementation. Anyway, thanks for taking the time to review!

[cristianscheid]

/backport to stable33

[cristianscheid]

/backport to stable32

[cristianscheid]

/backport to stable31

[cristianscheid]

/backport to stable30

[cristianscheid]

/backport to stable29

[cristianscheid]

Holding off on merging for now, we still have some internal discussion going on regarding this PR.

[backportbot]

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/58908/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick a9676604 d63f3e97 c286b826 d363057a ba267686 8f2cfe5f

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/58908/stable29

Error: Failed to check for changes with origin/stable29: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[backportbot]

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/58908/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick a9676604 d63f3e97 c286b826 d363057a ba267686 8f2cfe5f

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/58908/stable30

Error: Failed to check for changes with origin/stable30: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[backportbot]

The backport to stable31 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/58908/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick a9676604 d63f3e97 c286b826 d363057a ba267686 8f2cfe5f

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/58908/stable31

Error: Failed to check for changes with origin/stable31: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[artonge]

@cristianscheid after discussion with @sorbaugh, the API is fine, so I merged this PR. The backports will be tricky as the lexicon was introduced in 31 only, so they will need some adjustments.