Basic API Implementation

[Victor-IX]

Add a JSON file in the repo directly accessed by the Blender Launcher with GitHub API request to retrieve data like the list of Blender versions.

The primary goal of this is to create an easily editable endpoint for evolving data, allowing new data to be added without having to create a new version of the Blender Launcher each time.
This could be expended in the future if we want to cache the download, like to reduce request to the blender website.

[zeptofine]

With the index-selecting method we use to store the minimum stable build, The selected build will move as we add more builds

See 3.3 here:

Turns into 3.4 as I add a new build:

I suggest we don't save the minimum build as an index, but rather as the actual version, or a float

[Victor-IX]

I've started implementing a new API file for the stable build; I took the cache file with all the versions.
I think the best way to handle this will be to check if some builds present in the API file are missing in the user cache file and add them.

Because this will be done before the build gathering step, we save a lot of requests if the user doesn't have all the builds present in the API file.

I did a test, and gathering all the stable builds from 3.4 and after generated 50 requests, so this could be very useful for optimizing requests for first time user