clear bundling of deployment scripts and generated deployment artefacts

[christoff-buerger]

With time, the following feature-rich set of generic Bash scripts for day-to-day deployment of RACR-libraries developed (cf. issue #44 and #61 for details):

• list-scheme-systems.bash: detection of installed and supported Scheme systems
• list-libraries.bash: library detection
• parse-configuration.bash: automatic library configuration
• install-libraries.bash: library installation
• run-tests.bash: installation test
• run-program.bash: library execution

Considering the interdependence of these scripts and their increasing count, it would be good to bundle them in a deploying/deployment-scripts subdirectory, similar to the bundling of profiling scripts in profiling/profiling-scripts. Likewise, their names should be eased and aligned with the more convenient scheme applied for profiling scripts (cf. issue #67); a better naming would be:

• parse-configuration.bash => configure.bash
• install-libraries.bash => install.bash
• run-tests.bash => tests/run.bash
• run-program.bash => execute.bash

Furthermore, the cluttering of library directories with a new binary subdirectory for each Scheme system has to be improved, preferable by having a single binaries directory for each library, which in turn can containing a specific directory for each system's binaries.

[christoff-buerger]

New deployment scripts pass all tests; installation is consistent.