Our releases published to Packagist use version numbers with a
"v"-prefix, e.g. "v1.18.7".

The build-release script overwrites this with a version number without
the "v"-prefix, e.g. "1.18.7".

The result of this is that the composer.json in our release tar-files
does not match the composer.lock file in the repository nor the
composer.json that Packagist looks at.

Fix this by prepending a "v" to the version number when updating
composer.json.

* Externalize ldap

* Remove tests for LDAP-module

* Redirect old LDAP-class to ldap-module for backwards compatibility

* Externalize negotiate

* Install pecl-krb5

We need to include this in our travis-tests as long as we include the negotiate-module in the release

* Externalize consent module

Add an extra build step to specify the current version (the one we are building) in the composer.json file.

Before calling npm to install dependencies and build, we need to step into the installation directory. Also, node_modules and the stylesheet.js* byproduct can be removed in production.

Run `npm run build` now

- Remove .php_cs.dist file
- Add /data directory
- Add 'npm install'

Allows compatible IDEs to recognize the coding conventions for this project. E.g., indentation standards.