By letting the user select which group of plugins to load, an out of
memory condition can be avoided while still allowing all plugins to be
stored on the same disc.
This tries to make our code a bit more compliant with our code formatting
conventions. For future use, this is the command I used:
git ls-files "*.cpp" "*.h" | xargs sed -i -e 's/[ \t]*$//'
Display the names of the plugins being loaded, and display amount
of free memory while doing so. This should make it easier to spot
the case that too many engine plugins have been placed on the boot
medium.
