Create a dedicated Synchrony ingress

[bianchi2]

Currently, synchrony path is hardcoded in the ingress which make it impossible to deploy 2 instances of Synchrony using the same hostname but different paths. For example, it's not possible to deploy the following in one cluster:

https://my.confluence.com/instance1
https://my.confluence.com/synchrony-instance1

https://my.confluence.com/instance2
https://my.confluence.com/synchrony-instance2

While it's possible to define Confluence contextPath it's not possible to do so for Synchrony. This PR makes it possible to create a dedicated ingress for Synchrony where it's possible to use rewrite path annotations. Sadly, redefining Synchrony contextPath results in Synchrony not being able to start. With this change it'll be possible to define synchony path in the ingress as path: /synchrony1(/|$)(.*) and add nginx.ingress.kubernetes.io/rewrite-target: /synchrony/$2 annotation. This way requests to synchrony1 will go to Synchrony service on /synchrony path.

If synchrony.ingress.path is defined, we'll update system property passed to Confluence JVM accordingly.

Checklist

• I have added unit tests
• I have applied the change to all applicable products
• The E2E test has passed (use e2e label)