Project Hierarchy not show more then 100 child in Project Page

### Current Behavior

When I expand the parent project (Contains more than 100 children) on the project page, then in the GUI it only shows children upto 100, but when I see the list of children via API It shows all the projects if I use offset

curl -X 'GET' 'https://localhost:8081/api/v1/project//children?offset=400' -H 'accept
: application/json' -H 'X-Api-Key: '

but when I switch to Flat project view then I am able to see all the projects, but in the Hierarchy view, when I expand parent project then I am only able to child project upto 100 and project after 100 I am unable to see, but Via API if I use offset then I am able to see complete list

### Steps to Reproduce

1. Create a parent project
2. For that parent project create child projects (the count of child projects must be more than 100)
3. Expand the Parent project in the GUI
4. Review the number of child projects (Due to bug it only shows up to 100)
5. Use the API below API to fetch the list of child
**Child project 1 to 100:** curl -X 'GET' 'https://localhost:8081/api/v1/project//children' -H 'accept
: application/json' -H 'X-Api-Key: '
**Child project 101 to 200:** curl -X 'GET' 'https://localhost:8081/api/v1/project//children?offset=200' -H 'accept: application/json' -H 'X-Api-Key: '

the list of projects that you get in the second API call with offset=200 is not visible in the Hierarchy view GUI, but visible in Flat view

### Expected Behavior

When I expand the parent project (Contains more than 100 children) on the project page, then in the Hierarchy view GUI shows all the child projects (including after 100)

### Dependency-Track Version

4.8.2

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

_No response_

### Browser

Google Chrome

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported