Reintroduce automated acceptance tests

[Deltik]

Motivation and Context

Acceptance tests were previously disabled in 9d4aba8 because they were not scalable beyond an old base image and that old image stopped working.

Description

Instead of building an image to simulate a basic shared hosting environment, acceptance tests will now apply a state file on preexisting community images and then deploy e107 onto them.

For more realistic simulation, systemd with Podman is used in the initial few images that the new acceptance tests start up.

How Has This Been Tested?

The e107 acceptance tests now run on Ubuntu 20.04 and Ubuntu 22.04 for starters. They were previously running on a custom Ubuntu 20.04 image built one time two years ago.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (a change to man pages or other documentation)

Checklist

• My code adheres to the e107 code style standard.
• I have read the contributing document.
• I have added tests to cover my changes.
• All new and existing tests pass.

[codeclimate]

Code Climate has analyzed commit f6a225a and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (80% is the threshold).

This pull request will bring the total coverage in the repository to 34.6% (0.5% change).

View more on Code Climate.

[CaMer0n]

Thanks 👍