Neo4J browser

[filippomc]

Closes CH-32

Implemented solution

A new application has been added based on the neo4j reverse proxy -- see https://neo4j.com/docs/operations-manual/current/kubernetes/accessing-neo4j-ingress/

How to test this PR

harness-deployment ... -i neo4j -d [DOMAIN] and go to neo4j.[DOMAIN]

Sanity checks:

• [x] The pull request is explicitly linked to the relevant issue(s)
• [x] The issue is well described: clearly states the problem and the general proposed solution(s)
• [x] In this PR it is explicitly stated how to test the current change
• [x] The labels in the issue set the scope and the type of issue (bug, feature, etc.)
• [x] The relevant components are indicated in the issue (if any)
• [ ] All the automated test checks are passing
• [x] All the linked issues are included in one Sprint
• [x] All the linked issues are in the Review state
• [x] All the linked issues are assigned

Breaking changes (select one):

• [x] The present changes do not change the preexisting api in any way
• [ ] This PR and the issue are tagged as a breaking-change and the migration procedure is well described above

Possible deployment updates issues (select one):

• [x] There is no reason why deployments based on CloudHarness may break after the current update
• [ ] This PR and the issue are tagged as alert:deployment

Test coverage (select one):

• [ ] Tests for the relevant cases are included in this pr
• [x] The changes included in this pr are out of the current test coverage scope

Documentation (select one):

• [x] The documentation has been updated to match the current changes
• [ ] The changes included in this PR are out of the current documentation scope

Nice to have (if relevant):

• [ ] Screenshots of the changes
• [ ] Explanatory video/animated gif