[ENHANCEMENT] Do not generate `.env` within GAMA, but a more useful `settings.json`

[RoiArthurB]

Problem

While generating a VR-ready GAMA model, the plugin also generate two files :

• settings.json
• .env

The documentation advises moving the .env file in the middleware before running it to have the newly generated project displayed in the webplatform.

Note that when the SIMPLE tool generates a VR Gaml file, it also produces two additional files: settings.json, which contains information about the model to run and its execution conditions, and a .env file, which allows the modeler’s workspace to be added to the middleware. For this second file (which is hidden in the project folder), the user must copy it into the middleware folder.

Even if correct (the generated .env fills an absolute path in EXTRA_LEARNING_PACKAGE_PATH pointing to the GAMA project), managing hidden files can be a bit complicated, and users might need specific configuration in their .env which can be annoying to re-apply.

Proposed solution

Instead of generating the second file, the plugin might simply generate the settings.json with an absolute path pointing to the .gaml file and simply ask users to move this file in the webplatform.

This improvement would make the process simplier for user (no hidden file, no default parameters modified, etc) and less prone to creating issues in the way the platform works (like if the GAMA server isn't on the port 1000 by default ?).