ci: streamline the build and test process

[bassco]

Addresses some of the issues, and more, raised in #11

• Create preview images in Pull Requests
• Use conventional commits for release automation
• Add OCI labels to docker images
• Fix the README to enable local tests - compose is missing and so is the Makefile
• Fix the preview image creation step
• Delete preview container image and artifacts on merge or PR closing
• verify the renovate settings
• add a conventional commit labeler to the pull requests
• bump the toml version and references during release creation and tagging
• add mac silicon preview and release images for local development? Stretch goal
• added benchmark notes and samples script to run benchmark
• add a cargo deny github action to catch renovate version bumps that are not useful
• fix builds when features are changed - inconsistent code behaviour causes error
• fix the failing e2e exif test when features awc_client is enabled
• build dali and dali-awc in the preview image so that both versions can be used in tests

This is the error we recevied when we tried to cargo build --features aws_client

error[E0428]: the name `client` is defined multiple times
  --> src/commons/http.rs:66:1
   |
10 | pub mod client {
   | -------------- previous definition of the module `client` here
...
66 | pub mod client {
   | ^^^^^^^^^^^^^^ `client` redefined here
   |
   = note: `client` must be defined only once in the type namespace of this module

error: features `crate/hyper_client` and `crate/awc` are mutually exclusive
 --> src/main.rs:4:1
  |
4 | compile_error!("features `crate/hyper_client` and `crate/awc` are mutually exclusive");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This is caused because cargo treats features as additive. Because hyper_client was set as a default; it was also set when we tried the build the awc_client feature. The test to see which feature to enable had to be changed. To enable the default http_server, we tested the negated setting of features awc_client.

Cargo allows you to reference a crate from a local or remote git repository. By changing the Cargo.toml to a remote branch, I was able to determine which method is panicking.

The Cargo.toml change:

diff --git Cargo.toml Cargo.toml
index a52b08d..5103c5d 100644
--- Cargo.toml
+++ Cargo.toml
@@ -41,7 +41,10 @@ serde_qs = {version = "0.12.0", features=["actix4"]}
 config = "0.13.3"
 hyper = { version = "0.14.27", features=["full"], optional = true }
 hyper-timeout = { version = "0.4.1", optional = true }
-libvips = "1.6.1"
+# or use a git path or remote repo and branch
+# libvips = {git = "file:///absolute/path/to/git/repo", rev = "12345"}
+libvips = {git = "https://github.com/olxgroup-oss/libvips-rust-bindings.git", branch = "make-error-messages-explicit"}
+# libvips = "1.5.0"
 rexif = "0.7.3"
 lazy_static = "1.4.0"
 cfg-if = "1.0.0"

Running the tests produced.

$  ./scripts/dali-tests-runner.sh awc_client

e8f44d88da0e873de851d806ab60b3f4604ad9c9946ce3a8984887f3e866ad1a
Connection to localhost port 9000 [tcp/cslistener] succeeded!
    Finished dev [unoptimized + debuginfo] target(s) in 0.28s
     Running `target/debug/dali`
Connection to localhost port 8080 [tcp/http-alt] succeeded!
    Finished test [unoptimized + debuginfo] target(s) in 0.28s
     Running unittests src/main.rs (target/debug/deps/dali-d0d0bec70bf6e467)

<REDACTED_TEST_DATA_OUTPUT_FOR_BREVITY>

test test_get_exif_watermark ... FAILED

failures:

---- test_get_exif_watermark stdout ----
URL: <REDACTED_FOR_BREVITY>
Response:
ClientResponse HTTP/1.1 200 OK
  headers:
    "content-length": "21"
    "content-type": "text/plain; charset=utf-8"
    "date": "Sun, 12 Nov 2023 21:26:24 GMT"

thread 'test_get_exif_watermark' panicked at tests/utils/mod.rs:110:58:
Unable to read image from dali: InitializationError("VipsImage:new_from_buffer - Could not initialise VipsImage")
.....