Feature Request/Idea: Landing Page to show First-level Dataverses Collections only

Overview of the Feature Request

We would like to request a toggle-enabled function to show either:

1. All Dataverse collections and Dataset records, or
2. The "First-level" Dataverse collections/folders only, deeper-levels/sub-folders of Dataverse collections, i.e., Dataverse collections created under the First-level Dataverses, will be suppressed from displaying.

on the Dataverse landing page.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
All users including Curator, Guest, Superuser, and Sysadmin

What inspired the request?
To make the landing page more clean and concise, especially our institution aims at controlling the naming conventions of the First-level Dataverse collections.

What existing behavior do you want changed?
Not to show all the Dataverse collections on the landing page, but rather users can toggle between the two different choices.

Any brand-new behavior do you want to add to Dataverse?
Ditto

Any open or closed issues related to this feature request?
No

The payload names no files, tests, or entry points. Start by locating the landing-page collection listing in the TypeScript frontend and review how current Dataverse collections and Dataset records are loaded and displayed. Done means users can toggle between all records and first-level Dataverse collections only, with deeper collections suppressed in the latter view.