Add podman support

[depatl]

This change is 

[juledwar]

Great work!

We also need to update the Github workflows to test the MacOS path, it needs a
runs-on: macos-latest in there, but the test of the steps should be identical.

[juledwar]

Ok so there's a few things to fix:

1. The imports need formatting:
   cmd [3] | ruff check --select I --show-fixes dbtesttools
   dbtesttools/tests/test_pgfixture.py:1:1: I001 [*] Import block is un-sorted or un-formatted
2. The GH workflows are failing because Podman is not installed. This might help: https://github.com/marketplace/actions/install-podman
3. We need to add the macos runner to the test matrix in GH workflows.

The good news is that the tests all pass for me locally \o/

[juledwar]

I have no idea why your branch is failing the hatch build long_description check - I can recreate it locally but only on your branch and not on master!

But there's a bunch of other error output from the tests, which are still passing, so something is not quite right.

You also still need to make sure podman is installed and running.

[juledwar]

I suspect most of the errors are because podman is not up and running in the GH container that's running the tests.

[juledwar]

Depending on curl here is very bad, it means the tests won't pass if that site is down or something similar is broken.

[juledwar]

I don't understand why you're doing this, and the previous change. The scenarios declaration will run both of these automatically. This change means that the last file to to get imported overrides the scenarios as well, so for example on my machine the only scenario that gets run now is podman.

When running hatch run ci locally it should do exactly the same tests as Workflows would run, which is why the initial workflow file was as simple as it was, with the addition of the Python test matrix (which should arguably be declared in the Hatch matrix, but that's on my list of things to fix later).

In other words, we should not depend on GH Actions to run all of our tests to completion.

Let's go back to basics with this change and simply run up a worker with podman installed. See here https://github.com/marketplace/actions/install-podman for one in the marketplace.

I don't think you need all that docker-ce stuff as well, was there a reason to do it?

[juledwar]

Ah apparently that podman action is deprecated, crap. Back to manual installation.

[juledwar]

Also it was not indentation that cause the RST rendering break, it was the lack of a blank line. Here's a patch for you:

diff --git README.rst README.rst
index 7d3eae1..ea05e55 100644
--- README.rst
+++ README.rst
@@ -94,12 +94,13 @@ PG containers. You will need to do up to two extra things:
 
 If you want to use Podman instead of Docker engine you will need to follow
 these steps:
-1. Enable and start podman on your host
-```bash
-systemctl --user enable podman
-systemctl --user start podman
-```
-2. `export DBTESTTOOLS_USE_PODMAN=1` variable. 
+
+    1. Enable and start podman on your host
+    ```bash
+    systemctl --user enable podman
+    systemctl --user start podman
+    ```
+    2. `export DBTESTTOOLS_USE_PODMAN=1` variable.
 
 This code has been in use daily on a large project at Cisco for a few years
 now, and is very stable.

[juledwar]

I've made the changes I suggested and pushed a new branch up:
https://github.com/juledwar/db-testtools/pull/17/files
I also simplified the Actions config. You can copy the changes to your own branch or just merge mine.

[juledwar]

Closing in favour of #17