v0.0.35

[Benchmark] Fix wrong indent in hyper connector

v0.0.34: [UTest] Add tag [core][catalog][schema] for TEST_CASE("Table empty ac…

…cess")

- Add this tag to make it run as part of CI

v0.0.33: [Benchmark] Fix PostgreSQL timeout and clean-up.

- The *process* of the query within the PostgreSQL server can reach a
  timeout.  In that case, we kill the `psql` client.  This, however,
  does not stop the *process* within the server.  Consequently, clean-up
  after an experiment trying to run `DROP DATABASE` will trigger an
  error, as a table in the DB to drop is still in use.  To properly
  *"kill"* the server *process* we install *in PostgreSQL* a timeout
  with `set statement_timeout`.  This has the server kill *processes*
  that reach the specified timeout.
- The clean-up after an experiment must `DROP DATABASE` the table with
  the benchmark input data.  This was run incorrectly in one iteration
  of a loop right before the next iteration would attempt to that exact
  database, which would then have been dropped.  We generally change the
  structure of the code to use *local* `psycopg2` connections and always
  close them properly in a `finally` section.  Further, the
  `run_command()` no longer runs `clean_up()` itself.

v0.0.32

[WasmDSL] Remove constraint from `Variable`s default c'tor.

v0.0.31

[Benchmark] Use correct timeout value

v0.0.30: [Util] Fix in `unittest-parallel.py` script.

Exit with exit code 1 on failure of a test.

v0.0.29: [Coverage] Don't produce a JUnit report.

The `unittest` binary crashes with
```
unittest: /var/lib/gitlab-runner/builds/yS6csq8A/0/bigdata/mutable/mutable/third-party/catch2/include/catch2/catch.hpp:5918: virtual void Catch::CumulativeReporterBase<Catch::JunitReporter>::testCaseEnded(const Catch::TestCaseStats &) [DerivedT = Catch::JunitReporter]: Assertion `m_sectionStack.size() == 0' failed.
```
This error seems to be related to the Catch 2 JUnit reporter.  See
https://github.com/catchorg/Catch2/issues/1801 and
https://github.com/catchorg/Catch2/issues/1967.

To remedy this problem, we simply don't use produce a report anymore.
It was never used, anyway.

v0.0.28: [Benchmark] Refactor benchmark system.

Instead of using a different script for each experiment and DBMS to
benchmark, implement `connectors` to these DBMS's. The connector has a
method to execute an experiment with the given parameters and returns
the measured times.

In addition, the format of the YAML files of the experiments has been
refactored to contain all the information and parameters to execute them
on each connector.

`Benchmark.py` is refactored as well to read the experiment files and
execute them on each available specified connector, with possibly
multiple configurations.

Some more minor changes:
- Benchmark script now has the option to execute one (or multiple)
  specific experiments.
- The `run_id` of each experiment run is tracked and inserted into the
  database.

v0.0.27

[CI] Fix release asset upload path & variable substitution