(Suggestion)Sub project defragmentation

Is your feature request related to a problem? Please describe.
I cloned stride repo and looking around for a while to understand stride structure.
I was overwhelmed. There are a huge number of projects(csproj) in stride.

Describe the solution you'd like
I think most of them are awesome and pretty well organized.
But, I just want to suggest just one thing. => "Merge into small number of projects(csproj)"

Currently, more than 100 projects(csproj) exist in stride, and many projects have a too small number of code files.
Considering runtime dependency, that's too many numbers.
In my opinion, it makes build management worse, and a few people could handle the build and deploy process.

To promote many developers' contributions, stride's c# projects need to be merged.
If so, many developers would understand code more easily and then more contribute.

(Edit)I attach a good article to make it more clear and to prevent misunderstand because of my poor English.
https://stackoverflow.com/a/3618989/14519014

Thanks.

Start by mapping Stride’s more than 100 .csproj files and their runtime dependencies, then review how the build and deployment process is managed. Identify a smaller project structure that preserves organization and dependencies, and validate that the proposed merges work across build and deployment.