Fix useStartStopDaemon in launch script and allow config via conf file

Commit 5a1ee6eb added support for disabling use of start-stop-daemon
via a placeholder in the default launch script. Unfortunately, that
placeholder was subsequently broken in 81a47639.

This commit reinstates the placeholder and adds tests to verify that all
of the placeholders in the launch script can be replaced and that they
have the required default values. Furthermore, it also allows the use of
start-stop-daemon to be configured via USE_START_STOP_DAEMON in an
app’s .conf file. This allows the configuration to be changed after the
app has been built.

Closes gh-4985

spring-boot-docs/src/main/asciidoc/deployment.adoc

@@ -541,6 +541,10 @@ the default behavior in a script or on the command line:
  that the `stop\|start\|status\|restart` commands work, or to `run` if you just want to
  run the script in the foreground.
 
+|`USE_START_STOP_DAEMON`
+|If the `start-stop-daemon` command, when it's available, should be used to control the
+ process. Defaults to `true`.
+
 |`PID_FOLDER`
 |The root name of the pid folder (`/var/run` by default).
 
@@ -606,8 +610,8 @@ for Gradle and to `${project.name}` for Maven.
 |The `chkconfig` section of "`INIT INFO`". Defaults to `2345 99 01`.
 
 |`useStartStopDaemon`
-|If the start-stop command should be used to control the process when it's available.
- Defaults to `true`.
+|If the `start-stop-daemon` command, when it's available, should be used to control the
+ process. Defaults to `true`.
 |===