Description of problem (please be detailed as possible and provide log
snippests):

Need commit hash in package json and logs


Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Yes, this would help in debugging by development teams

Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?

Yes

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:

Inside noobaa logs there should be a commit hash next in the package.json and in the logs.

from the upstream logs:
$ kubectl logs pod/noobaa-core-0 | grep "Version"
Version is: 5.10.0-82e1120

Feb-3 15:14:29.534 [BGWorkers/38]    [L0] core.server.bg_services.cluster_hb:: writing cluster server heartbeat to DB. heartbeat: { version: '5.10.0-82e1120', time: 1643901268536, health: { usage: 0.04878745969330378, os_info: {
      { _id: 61fbe1a7d9a8fa002ba4ae1f, heartbeat: { version: '5.10.0-82e1120', time: 1643901268536, health: { usage: 0.04878745969330378, os_info: [Object], storage: [Object] } }, services_status: { dns_status: 'OPERATIONAL', ph_status: { status: 'OPERATIONAL', test_time: 1643901269 } } }

$ kubectl exec -it pod/noobaa-core-0 -- cat /root/node_modules/noobaa-core/package.json | grep version
  "version": "5.10.0-82e1120",

and in the downstream the version is:
kubectl exec -it pod/noobaa-core-0 -- cat /root/node_modules/noobaa-core/package.json | grep version
  "version": "5.10.0

Actual results:
"version": "5.10.0

Expected results:
"version": "5.10.0-82e1120",

Additional info: