Add swap file adjustment for webapp build

[AlvinSchiller]

• reworked the webapp build script to automatically calculate and adjust the swap if needed (for low memory devices)
• raised the minimum memory used for the build for better performance
• added webapp build option to installation (instead of manually trigger it afterwards)
• added an action to test if the webapp build is successfull after changes

Tested on a RPI 3 A+ and a RPI Zero W with 512MB Ram

[AlvinSchiller]

There are some deprecation and linting warnings that should be addressed in another PR

[pabera]

Question: How can we use min 512MB for Node when the entire device only has so much? E.g. Pi Zero 2 only has 512MB. I guess you try to max out the swap size in the next step with this approach?

[AlvinSchiller]

The "missing" memory is compensated by the swap.
I made a few testruns with the old memory steppings and using only 256 MB was causing failures during build.
So i used the next step (512 MB) from the old code , which didn't faild so far in multiple tests.
This is also already documented.

The 3 A+ has only 512MB physical ram too and it works well so far.

[AlvinSchiller]

Further information for commit use prebuilt webapp bundle also for develop

The bundled webapp was used for installations from the official repos main branch.
For the official repos develop branch the flag "ENABLE_WEBAPP_PROD_DOWNLOAD" was forced to false (see below), which resulted in installing node but didn't download the prebuilt bundle. Only if the user declined to install node the bundle was used.

RPi-Jukebox-RFID/installation/routines/customize_options.sh

Lines 287 to 289 in 6551669

	if [[ "$ENABLE_WEBAPP_PROD_DOWNLOAD" == "release-only" ]]; then
	ENABLE_WEBAPP_PROD_DOWNLOAD=false
	fi

As the webapp is now build during installation and the official repos release branches (main and develop) are most likely not directly used for development, but could be used by Builders to try new features / bugfixes, these will now handled the same.
The bundled webapp will be downloaded and Node will NOT be installed.
Developers should start the installation directly with the feature branch / fork defined.

The docs have been updates accordingly.

[pabera]

What about unifying this with show_slow_hardware_message ?

[AlvinSchiller]

Did think about this too.
Which message should we use?
And do you want to import the helper script or just duplicat the message?

[pabera]

Let's not merge it and instead give a little bit more support

Building the Web App takes significantly more time. In case it fails, check the documentation to trouble shoot.

[pabera]

You don't have to write a second time, that the hardware is slow ;-)

[AlvinSchiller]

This is ready for final reviews