chore(qa): increase it test client timeout

- glassfish fails to shutdown if a socket timeout occurs
feat(retries): implement defaultNumberOfRetries property

Related to: #CAM-2539
test(engine): failing testcase for "isDeployChangedOnly"

related to #CAM-2213
chore(engine): make fields static
chore(defaultRetries): provide a further test case

related to CAM-2539
fix(engine): retrieval of unchanged process keys on deployment

related to CAM-2213
test(engine): test call activity with async start event in subprocess

related to CAM-2566
chore(distro): check jdk version inside startup script(unix)
chore(engine-spring): java config in SpringProcessEngineTestCase

related to CAM-2646
fix(history): distinguish between events

-- also fixing some typos in method and variable names

Related to: #CAM-2365
chore(engine): make job executor hint configurable

- if configured, disables hints for exclusive jobs
- makes parallel execution of exclusive jobs less likely in cases where a
  job is a follow-up after an asynchronous signal was received
- timers that are due within the job executors wait time are nevertheless
  hinted at

related to CAM-2522
fix(engine): repair job lock state when setting retries

- reset the job lock when it has become inconsistent
- cases are:
  - retries are 0 but a lock is set (i.e. lock owner or expiration time)
  - a lock owner but no expiration time is set

related to CAM-2710
feat(engine/rest): add expression to task query

- allows to use expressions for following attributes of a task query:
  assignee, assgineeLike, owner, involvedUser, candidateUser,
  candidateGroup, candidateGroups, createdOn, createdAfter,
  createdBefore, dueDate, dueAfter, dueBefore, followUpDate,
  followUpAfter, followUpBefore
- expressions are also available by the REST API

related to #CAM-2629
chore(engine): improve spin support
chore(cycle): remove cycle from platform

related to #CAM-2714
Merge branch 'master' of github.com:camunda/camunda-bpm-platform
chore(rest): filter NONE and ALL permission names on authorizations

- we now distinct between the ALL permission in the backend and
  the ALL permission in the frontend

backend:
  - ALL granted means that all possible permissions are granted
  - ALL revoked means that at least on permission is revoked

frontend:
  - ALL granted means that all possible permissions are granted
  - ALL revoked means that all possible permissions are revoked

- NONE is always filtered cause it is always granted and has no
  useful meaning for the front end

- this leads to following permission names lists:

1. ALL granted in backend => [ "ALL" ] in frontend
2. ALL revoked in backend => [ "ALL" ] in frontend
3. READ, UPDATE revoked in backend => [ "READ", "UPDATE" ] in frontend

related to #CAM-2768
feat(engine-rest): add OPTIONS request to filter resources

- checks engine authorizations for the offered methods

related to CAM-2766
feat(sentry): first implementation of sentries

This commit adds the implementation of sentries.

related to CAM-2373
feat(engine): support setting serialized variable values

Suppport setting serialized variable values is all setVariableX(...)
APIs

related to #CAM-2484