obj: fix zone size calculations

The calculations for total available heap size for user
allocations didn't take all possible metadata into account,
leading to situations where for certain heap sizes
the zone size was too large by a chunk.

rpmem: don't stat a non-local replica during recovery

Its ->path will be null, which is doomed to fail.

Ref: pmem/pmdk/issues/4231

obj: fix lock release order in palloc publish

Given a following (sorted) collection of heap actions on
memory blocks 1, 2:

Alloc 1.1, Alloc 1.2, Free 1.3, Free 2.2, Free 2.5

The algorithm looks at every action and acquires lock
for that memory block if that lock wasn't acquired previously.
In this example, two locks would be acquired (2 blocks).

After this is done, the actions are processed. Next,
the actions are iterated over again, in the exact same order,
and an "on_process" callback is invoked and the lock for
that action is dropped.

And this was the problem. The locks were being dropped before all
actions for the same memory block had their "on_process" callback
invoked.

In this example, the order of operations would be:

lock(m.1);
lock(m.2);

process_actions();

on_process(1.1);
unlock(m.1);
on_process(1.2);
on_process(1.3);
on_process(2.2);
unlock(m.2);
on_process(2.5);

This left some of the on_process() callbacks unprotected, leading
to unintended races.

This patch fixes the problem by unlocking on last block.
Now, the order of operations will be:

lock(m.1);
lock(m.2);

process_actions();

on_process(1.1);
on_process(1.2);
on_process(1.3);
unlock(m.1);
on_process(2.2);
on_process(2.5);
unlock(m.2);

This bug triggered an ASSERT() in debug builds, and in release
builds it might have made runtime calculations related to recycler
inaccurate, possibliy negatively impacting fragmentation.

pmem: fix pmemcheck support on platforms with eADR

obj: fix potential NULL-dereference in ulog_store

In situations where the total number of entries to be stored in the
ulog was an exact fit for the total capacity of the log,
the algorithm was unnecessarily trying to zero-out a non-existent
subsequent ulog. This triggered an ASSERT on debug builds and crashed
on NULL-dereferencing.

obj: fix transient redo log of more than 64 entries

All transient actions in a single memory operation after 64th
weren't being applied correctly because the non-cached capacity
of a transient ulog wasn't being updated alongside the cached
capacity - this caused a problem where the vast majority of
code used the cached version, but the actual applying method
used the uncached one.

The only public API that could conceivably trigger this is
pmemobj_set_value when used on volatile variables.

common: fix util_read/util_write on Windows

include df in testsuite output

We want to know filesystem type and free disk space.

test: force-disable pmemcheck in obj_root test

doc: automatic stable-1.5 docs update

doc: fix formatting of pmreorder man page

This small change unbreaks the whole man page.

doc: automatic stable-1.5 docs update

doc: fix pmem_errormsg description

doc: automatic stable-1.5 docs update

fix manpage sections references: lib* are in section 7 not 3

Fixes pmem/issues#1130.

obj: fix pmemcheck marker in pmemobj_tx_wcsdup