Remove Nuget for smoother development (Does not mean abandon Nuget for getting packages)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Nuget while it is a great package manager for C# tools and libraries, it can of course have its downsides such as loading other templates. Android and other platforms get the Android get the page size limit but that could be solved by removing the package manager as a dependency and instead using the libraries

Describe the solution you'd like
A clear and concise description of what you want to happen.

the issue with most things that could be solved by removing the package manager as a dependency and instead using the libraries, while you can still package them seperately, it makes it easier to make changes to Stride3D later down the line if Nuget is no longer usable.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

while you can still package them seperately, it makes it easier to make changes to Stride3D later down the line if Nuget is no longer usable. or if things change in development, switching to another package manager would take around 3-5 months or more

Additional context
Add any other context or screenshots about the feature request here.

Stride3d is a great game engine for making games i feel like it could do better without Nuget being a dependency and more with a packaged application that can be portable and easier to use anywhere and allow for developer to build their applications on other platforms

Here are some questions that can aid in the description of the feature request:

1. • What are the use cases?: it would help speed up development
2. • What kind of options or settings are expected or wanted?: No changes as of now just a removal of Nuget
3. • What would the (pseudo) code look like?: it wouldn't look much different, only a few change
4. • Does the feature affect behavior in the editor?: Nope. not at all. it would only affect speed of how the application runs, it might make stride3d faster then it already is

• If so, how should this look in the editor?: [Answered above]
• Is there a component or data structure involved?: No
• What kind of documentation is needed or needs to be updated?: Nope
• Should there be an example project?: Nope

one more thing to add before anything, i do believe projects themselves would be in the same folder or in the "../Appdata/local/Stride3d/Example Projects/"

i would like some thoughts on this

No files, tests, or entry points are identified in the issue. Start by mapping how NuGet dependencies are declared and restored across the Stride repository, then determine the scope of replacing them with bundled libraries while preserving package distribution. Done would require an agreed design and working development and packaging flows across the affected platforms.