Setting the default user to run the services to graylog2 in init.d-graylog2-server and init.d-graylog2-web-interface

The graylog2 user is created upon installation, so instead of these services being run as root changing them
to be run as a non-previledged user.
Updating to 0.20.0-preview.5 for graylog2-server.spec and graylog2-web-interface.spec
Adding the lib_dir and CLASSPATH variables to sysconfig-graylog2-web-interface
Running the graylog2-web-interface as the root user and breaking the startup command into multiple lines in init.d-graylog2-web-interface

The additional variables in sysconfig-graylog2-web-interface lightens the complete dependency on
variables declared in init.d-graylog2-web-interface. These variables are not likely to change.

In an attempt to run the web-interface as an unpriviledged user, configured in init.d-graylog2-web-interface,
resulted in the server not being able to create the syslog inputs. Running it as the root user is now the
permanent workaround.

Breaking the startup command arguments into multiple, escaped lines adds readability and allows for bulk
insert and removal of different arguments.
Running the graylog2-server as root user from unpriviledged graylog2 user in init.d-graylog2-server

While starting up the server as the graylog2 user creating the log inputs failed to bind the ports
because the user didn't have permissions to do so. May be able to work around this in the future,
but for now running it as the root user ensures all functionality is present.
Removing the graylog2 user and group management from graylog2-server.spec and graylog2-web-interface.spec

Testing with running the server and the web-interface as the graylog2 user failed as starting up the
server returned an error because it couldn't bind the syslog input to 0.0.0.0:514 UDP. For simplicity
both packages are running as the root user.