Analyze if we can skip GitLFS based on GitHub limits

[JaXt0r]

Let's check if we can remove LFS and it's bandwidth costs.

We need to assess:

• What's the overall size of current LFS data
• Is it matching with gut limits? https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github

Then we can think about removing it. But! Whenever we upload a new version of a file, it will be added to the repository again. In total. So if we have a 50MB file uploaded with one binary change, it will be another 50MB on the repository for this binary file.

[JaXt0r]

You can upload larger binary files into a separate repository and reference it in Unity via a Git package. https://docs.unity3d.com/Manual/upm-git.html

Tested and works for OcclusionCulling data and binary dependencies (.dll/.so)

Feel free to check on our implementation and reuse it to save 5€ per month. https://github.com/Gothic-UnZENity-Project/Gothic-UnZENity-fork-deprecated/pull/1