Add a new function to upgrade the store from version "0" to "1".
Except the addition of the 'version' file there is no difference
between the two versions and thus creating said 'version' file
is all the store upgrade does. This can still be useful, because
it can be used as a marker, e.g. the manager can use it to clean
up the store once when upgrading from version 0.

Add version information to the on-disk store and expose that
information via a new "version" store object property. The
on-disk information is stored in a new 'version' file, that
is located at the root of the store. In case no such file is
found, the store version is defined as 0 (zero).
When a store is opened, and the root of the store is completely
empty (i.e. no sub-directories or the version file is present),
the store is assumed to be new and is initialized by creating
the 'version' containing the BOLT_STORE_VERSION number.

Convert the store use the GInitable interface. This prepares for
store on-disk initialization that can fail. Currently, nothing
is actually done in initialize and thus it will never fail.

Adapt all tests to check for potential store creation errors and
also convert the manager's store initialization method to handle
the error.

Instead of initializing the store in the basic object init method,
create a new method that bundles all store related initialization
and call that from bolt_manager_initialize. This prepares for the
possibility that store initialization can fail.

Checks for various invocations of bolt_renameat, including error
reporting.

Add a simple wrapper for renameat(2), mainly for GError based error
reporting.

Check basic functionality and error reporting for bolt_mkdirat.

Add a simple mkdirat(2) wrapper for GError based error reporting.

Simple checks that we get the expected errors for non existent
files and files containing unexpected data.

Extract the test table for string to integer conversion,
which was duplicated in two different test cases.

Extract the test table for string to unsigned integer conversion,
which was duplicated in two different test cases.

Basic test cases for writing an unsigned integer to disk. The
data is verify via bolt_read_unit_at.

Small helper which writes a plain unsigned integer to a file.
Uses bolt_write_file_at internally.

Test case for bolt_read_uint_at. Duplicates the test table for
test_str_parse_uint for now.

Basic checks for bolt_write_int_at. Uses bolt_read_int_at to
verify the integer got written properly.

Add a new helper that writes a plain int to a file, internally
using bolt_write_file_at.

Test case for bolt_read_int_at. Duplicates the test table for
test_str_parse_int for now.

Re-implement bolt_file_write_all in terms of bolt_write_file_at,
since open (...) <=> openat (AT_FDWCD, ...).

Basically the same test as test_io_file_write_all: write data, check
it is all there, overwrite the file, check it got overwritten and
truncated.

This is like the existing `bolt_file_write_all`, except it takes
a file descriptor to a directory to be able to specify the parent
directory. Will create a new file or overwrite an existing. Does
not do atomic io or the rename-to-do-atomic-io rename dance.

Create a define of open flags that is typically used to create or
overwrite new files; with a plain text spelling out of the flags.
This is done so that they can be reused in other functions.

Analogous to bolt_read_int_at, but for unsigned integers; uses
bolt_read_value_at and bolt_str_parse_as_unit internally.

Change a stray podman usage to docker, since podman is not even
installed and the image is built with docker.

The ORG argument needs to be set as well.

Specify the missing build arguments for the coverity container.

Only meant to be run from schedule pipelines, since there is a
rate limit for coverity.

Add a new container to perform coverity analysis, i.e. it fetches
the coverity distribution. Add a new coverity.sh script to actually
perform the analysis and upload the results.

Add a new test for `bolt_str_parse_as_uint` based on the existing
tests for `parse_as_xxx`.

Add a new helper to parse a string as unsigned integer (uint).
Internally uses the 64 bit based uint64 parse method and then
checks the parsed value fits into an unsigned integer.

For both, parse_uint{32, 64}, check that `errno` is properly set.

The `bolt_str_parse_as_uint32` method uses the uint64 based method
to parse the string and then afterwards checks for the parsed
value overflows an uint32. In that case also set the errno value,
to be consistent with the uint64 parse method.

The value we are checking is a signed 'int', so use the proper
comparison function, i.e. `g_assert_cmpint`.

If codespell is available, as it should be in the Fedora container,
run in on the source.

Can then be used by docker-build.sh to spell check the source.

Fix all spelling mistakes uncovered by codespell.

This makes codepsell happy without using a German dict.

Fedora 30 is actually EOL already. Use the current stable (F32).

Check that if bolt_domain_can_delete returns FALSE, the store does
indeed refuse to delete the domain.