Upgrading deegree webservices

From 3.5.x to 3.6.0

NOTE: Before upgrading to version 3.6 install the latest version of 3.5 (at least 3.5.8) and verify your active configuration!

Issue #1616/PR #1708: The password format for the file console.pw changed. Users need to re-create their password used by the deegree admin console when upgrading to deegree 3.6.

NOTE: Before upgrading to version 3.5 install the latest version of 3.4 (at least 3.4.31) and verify your active configuration!

Issue #1495/PR #1496: The XML schema location has been changed. To enable code completion for the last available feature set within your IDE while editing the deegree configuration files you have to change the schema location to https://schemas.deegree.org/core/3.5/.
Issue #1017/PR #1337: Requires changes to all JDBC database connection files using Apache DBCP:
- the driverClassName changed from org.apache.commons.dbcp.BasicDataSource to org.apache.commons.dbcp2.BasicDataSource (Notice the 2 in the package name dbcp2!)
- the maxActive configuration option has been renamed to maxTotal
- the maxWait configuration option has been renamed to maxWaitMillis
- the removeAbandoned configuration option has been replaced by removeAbandonedOnBorrow and removeAbandonedOnMaintenance
Issue #1157/PR #1441: Syntax of ehcache configuration changed
- ehcache Migration Guide
- XML configuration

Issue #1102/PR #1442: deegree no longer sends a version header by default in HTTP response.
Issue #1494/PR #1489: for protecting deegree's REST API against un-authorized access use the HTTP header or parameter instead of BASIC HTTP Authentication.

ensure that the PostgreSQL database used for SQLFeatureStore with BLOB mode have the SRID set.