Expose CLI version and build metadata consistently

Nobody has claimed this yet.

### Reason/Context

The CLI version is currently hardcoded and only exposed through the `version` command. That makes source-built, nightly, and packaged binaries harder to identify when debugging user reports.

### Description

Since the project already uses a Makefile, the build system can inject version and commit metadata at build time. This keeps release binaries tied to their Git tag, while still making local/source builds identifiable by commit.

Something like having

```
Microcks CLI 1.0.2-43-g1dad150-dirty
Commit: 1dad150
```
for the local builds

and for release builds which are sourced from the release tags

```
Microcks CLI 1.0.3
Commit: 1dad150
```

Start with the CLI's existing version command and the Makefile, then trace how source, nightly, and release binaries are built. Define the expected version and commit metadata for each build type, and verify that the command reports both consistently for local and tagged builds.

Written by the indexing model from the issue text.