[PER-10314] Make folder click show containing files

[aasandei-vsp]

STEPS TO TEST UNLISTED SHARES FLOW

Anonymous user:

1. Create an account or use an existing one and log in

2. Create or use a folder that contains other folders and files, inside the folders, create more folders, so you can have a tree structure like of folders and files.

3. Create share link for the "root" folder, the one you created first and make sure the link type is "Anyone can view"

4. Open a tab in incognito mode and paste the generated link

5. Go through folders by single clicking them
   EXPECTED: Being able to navigate forward inside the folder structure.

6. In a folder with multiple files, click on a file

7. Use the arrows to go through all the files in the folder

8. Download one of the files

9. Click the back arrow
   EXPECTED: It should get back to the containing folder

10. After you have clicked several folders, click a folder name in the breadcrumbs.
    EXPECTED: The breadcrumbs cut to that specific folder and you get the see the folder/files inside it

Signed in user:
Repeat the steps above, only 4 changes:
4. Open a new tab and log in with a different user and then paste the generated link

STEPS TO TEST EXISTING SHARES FLOW:
Anonymous user:

1. Create an account or use an existing one and log in
2. Create or use a folder that contains other folders and files, inside the folders, create more folders, so you can have a tree structure like of folders and files.
3. Create share link for the "root" folder, the one you created first and make sure the link type is "Restricted"
4. Open a tab in incognito mode and paste the generated link
   EXPECTED: "Create account" modal should appear

Signed in user:
Repeat steps 1 through 3, then:
4. Open a new tab and log in with a different user and then paste the generated link
EXPECTED: "Accept share" sticky footer should appear.

OTHER FLOWS THAT HAVE BEEN AFFECTED BY THIS CHANGE
Private files/Shared files/Public files/Public gallery

1. Create an account or use an existing one and log in
2. Create or use a folder(in one of the sections mentioned above) that contains other folders and files, inside the folders, create more folders, so you can have a tree structure like of folders and files.
3. Click through the folder structure
4. Click on files to preview, try to navigate using the arrows, edit details, download

[codecov]

Codecov Report

❌ Patch coverage is 51.85185% with 39 lines in your changes missing coverage. Please review.
✅ Project coverage is 47.05%. Comparing base (7beb31a) to head (4fa3125).
⚠️ Report is 12 commits behind head on main.

Files with missing lines	Patch %	Lines
...omponents/share-preview/share-preview.component.ts	40.90%	12 Missing and 1 partial ⚠️
...rowser/components/file-list/file-list.component.ts	58.62%	12 Missing ⚠️
...red/components/breadcrumbs/breadcrumb.component.ts	0.00%	5 Missing ⚠️
src/app/shared/services/data/data.service.ts	44.44%	5 Missing ⚠️
...ponents/file-list-item/file-list-item.component.ts	0.00%	3 Missing ⚠️
...ed/components/breadcrumbs/breadcrumbs.component.ts	90.90%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #805      +/-   ##
==========================================
+ Coverage   46.95%   47.05%   +0.10%     
==========================================
  Files         372      372              
  Lines       11444    11494      +50     
  Branches     1896     1907      +11     
==========================================
+ Hits         5373     5409      +36     
- Misses       5882     5899      +17     
+ Partials      189      186       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[slifty]

This does all look great and thank you for the easy to review commits!

Some notes about commit messages though, inspired by the great guidance of https://cbea.ms/git-commit/:

1. These title lines are all are quite long (and wrap to the body) -- ideally subject is just 50 characters
2. The issue number is in the subject, but we might want to consider putting this one line after the body <-- you aren't alone in doing this, but saves space for the subject line for content, while keeping the issue context in the commit overall.
3. There is no body, for the most part (what goes in the body is a bit of an art, but generally explaining the "why does this commit exist" is the point.

So for instance you might consider a message like this

Add breadcrumbs for unlisted shares

Some unlisted shares have a folder tree structure.  This commit adds
support for handling that case and also creating the navigation logic
within that tree structure.

Issue PER-10314 { title of the issue }