build(dockerfile): ensure that docker in installed so that commitsha is read during build

[machi1990]

This follows up on #1321, notably #1321 (comment)

Description

Verification Steps

Checklist (Definition of Done)

• All acceptance criteria specified in JIRA have been completed
• Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)
• Documentation added for the feature
• CI and all relevant tests are passing
• Code Review completed
• Verified independently by reviewer
• All PR comments are resolved either by addressing them or creating follow up tasks
• Required metrics/dashboards/alerts have been added (or PR created).
• Required Standard Operating Procedure (SOP) is added.
• JIRA has been created for changes required on the client side

[machi1990]

/cc @valeriiashapoval

[miguelsorianod]

Do we need that in any other image/environment? @machi1990

[miguelsorianod]

This is very surprising behavior as all I found in the Go documentation is:

Version control information is embedded if the go command is invoked in a directory within a Git, Mercurial, Fossil, or Bazaar repository, and the main package and its containing main module are in the same repository. 

Which does not mention the need of having git installed

[codecov]

Codecov Report

Merging #1333 (a86628a) into main (3a5738c) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1333   +/-   ##
=======================================
  Coverage   83.66%   83.66%           
=======================================
  Files         139      139           
  Lines       12436    12436           
=======================================
  Hits        10404    10404           
  Misses       1666     1666           
  Partials      366      366           

Flag	Coverage Δ
unittests	83.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[machi1990]

This is very surprising behavior as all I found in the Go documentation is:

Version control information is embedded if the go command is invoked in a directory within a Git, Mercurial, Fossil, or Bazaar repository, and the main package and its containing main module are in the same repository. 

Which does not mention the need of having git installed

Yes, I think the documentation could have been better on that regard.
Now everything relies on the assumption that users can make when reading .."Version control information is embedded if the go command is invoked in a directory within a Git, Mercurial, Fossil, or Bazaar repository" that if you are in a vcs repo, then you must have a corresponding vcs tool installed.

The requirement of having git initially caused some issues e.g golang/go#51723