[Design question] Should file tree browser be available on the top level Repository page?

Context

In the MVC of the file tree browser, the file tree browser was not included in the Project Overview Page per #19530 (comment 2432121108). However, the file tree browser is available on the top level directory Repository page. Both pages show the same root directory for the repository, however 1 allows users to see the file tree and one does not. This is inconsistent.

Project overview page	Repository top level directory page
Directory: test-project-general File tree browser: hidden	Directory: test-project-general File tree browser: visible

Research questions

1. Why do users want to see this at the project root?
2. Do external users have the same needs as our internal ones?

Design questions

• Is the file tree browser useful on the Repository top level directory page?
• What are consistency considerations between the Project overview page <> Repository top level directory page?
• Should the file tree browser appear on the Project Overview page (information dense, one of the most trafficked pages in GitLab)?
• If we did add it to the project root, what's the core difference between the repo file list vs. the repo file tree?
• Do we want the file tree to be usable when not in nested folders?