Add support to interact with a local podman installation

[NotTheEvilOne]

What this PR does / why we need it:
This PR adds support to interact with a local podman installation.

Which issue(s) this PR fixes:
Closes #199
Closes #200

[codecov]

Codecov Report

❌ Patch coverage is 86.32219% with 45 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.13%. Comparing base (d3ea02a) to head (bf61ccb).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
src/gardenlinux/oci/podman.py	81.30%	23 Missing ⚠️
src/gardenlinux/oci/__main__.py	84.15%	16 Missing ⚠️
src/gardenlinux/oci/container.py	91.17%	3 Missing ⚠️
src/gardenlinux/oci/podman_context.py	95.52%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #211      +/-   ##
==========================================
- Coverage   91.41%   91.13%   -0.28%     
==========================================
  Files          49       51       +2     
  Lines        2585     2887     +302     
==========================================
+ Hits         2363     2631     +268     
- Misses        222      256      +34     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[vivus-ignis]

Please add tests. I've also added some suggestions.

[NotTheEvilOne]

Please add tests. I've also added some suggestions.

Code is now ready for review, I would highly appreciate your feedback @vivus-ignis.

[vivus-ignis]

The code looks good to me, but the user experience of the gl-oci has a room for improvements. It's not obvious what is this tool is for in general and how to use it (see my comments on naming).

[vivus-ignis]

Please add proper cli error messages when wrong arguments are passed to pull (maybe it also applies to other subcommands).

I would also add tests for non-happy paths, at your discretion however.

[NotTheEvilOne]

Please add proper cli error messages when wrong arguments are passed to pull (maybe it also applies to other subcommands).

Please elaborate in more detail what you mean with "proper cli error messages":

Usage: gl-oci pull-container [OPTIONS]
Try 'gl-oci pull-container --help' for help.

Error: Missing option '--container'.

This is the default output and already pretty detailed. Based on the audience of the CLI tools I would expect our users to be able to figure out what option is missing.

Furthermore please consider to open an issue if error messages may not contain the details you would expect. This is out of scope for this PR.

[vivus-ignis]

Proper CLI error message (and actually a proper error message in general) is a message that gives a hint to a user on what he/she can do next to fix the problem. Here's an example from docker

docker pull foo:bar
Error response from daemon: pull access denied for foo, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

In my opinion, "None" is not an error message at all.

[vivus-ignis]

LGTM