Turn libunwind off for valgrind tests

It's set in our CI scripts to 0 by default, it's unnecessary to duplicate it.

docker: add missing hub package

it wasn't added into Fedora 34, while we bumped 'doc' job to use latest Fedora.

CI: use Fedora 34 instead of 32, since 32 is EOL now

as long as it's working it can run in nightly build.

Merge stable-1.12 into stable-1.13

Fix Docker image version(s) in CI

CI: update valgrind to 3.17

It's copy pasted from pmemkv (0d764bd).
Without this fix doc job may fail if image changed for master.

This solution is copy-pasted from pmemkv (70cd9e4).
Without this change PRs created against any stable branch may end up failing,
because it uses 'latest' image, instead of proper stable (e.g. '1.13') image.

We now use x.y.z format for all releases and the regex did not work well
with 1.13.0 release.

our pmemcheck tool was recently rebased to upstream 3.17 version.
It contains at least few useful bug fixes, e.g.:
https://bugs.kde.org/show_bug.cgi?id=426144
https://bugs.kde.org/show_bug.cgi?id=407764

Avoid libunwind on valgrind tests

disable 'maybe-uninitialized' compiler flag

in tests, examples and benchmarks - it produces many false-positives.

tests: add drd/memcheck suppressions

Taken from https://github.com/pmem/pmdk/commit/02762f3eba6f3f69f81343925c82db6b0200a426

inline_string: add missing specialization for total_sizeof

inline_string: implement copy assignment operator

Older compilers have problems with using assignment operator
from the base class.

[inline_string] Differentiate inline_string on PMEM and DRAM

instead of basic_inline_string so that there is no implicit
copy of inline_string when string_view is passed.

Authored by: Igor Chorazewicz

Fixes

tests: remove Testcase1 object before exiting from test.

it wasn't added during one of merge's.

ref. 1c37736e

next may be end() in case of the last key (or in case of concurrent erase).

CI: extend weekly runs with ASAN/UBSAN on fedora rawhide