Add tag / build reference api

[filippomc]

Closes CH-47

Implemented solution: the build id (as git commit hash) is now extracted by harness-deployment and added to values.yaml. The common service exposes it and the tag. Added an example on samples microservice

How to test this PR: start samples.DOMAIN and verify that is shows the tag and build id as in the screenshot.

Sanity checks:

• [ ] The pull request is explicitly linked to the relevant issue(s)
• [ ] The issue is well described: clearly states the problem and the general proposed solution(s)
• [ ] From the issue and the current PR it is explicitly stated how to test the current change
• [ ] The labels in the issue set the scope and the type of issue (bug, feature, etc.)
• [ ] All the automated test checks are passing
• [ ] All the linked issues are included in one milestone
• [ ] All the linked issues are in the Review/QA column of the board
• [ ] All the linked issues are assigned

Breaking changes (select one):

• [ ] The present changes do not change the preexisting api in any way
• [ ] This PR and the issue are tagged as a breaking-change

Possible deployment updates issues (select one):

• [ ] 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
• [ ] The changes included in this pr are out of the current test coverage scope

Documentation (select one):

• [ ] 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

[filippomc]

@zsinnema the version of this api is representative of the deployment so it's the same for all applications. It is indeed implemented only for the common app, what the samples app does here is to display the value in the ui.

[zsinnema]

@zsinnema the version of this api is representative of the deployment so it's the same for all applications. It is indeed implemented only for the common app, what the samples app does here is to display the value in the ui.

what I meant @filippomc is that we don't need an application to show the version number. We can just show it in the keycloak login screen.....

[filippomc]

@zsinnema I think it can be a good idea to show the version in the keycloak login screen, but we are not customizing the keycloak theme on ch, which makes updates simpler. Also derived applications have their theme and might not want to show the version there.