Fix log inside pruning storer

[bogdan-rosianu]

fixed the condition when a log in printed and also changed the log level. The condition was not right as the counter is relevant only if a persister is re-opened and appended inside active persisters. Otherwise, the function doesn't affect the state of active persisters.

Testing scenarios & Acceptance criteria:

1. Log no longer displayed when not needed. For example, the transition from epoch 0 to epoch 1 should not trigger the log
2. Log still displayed when a shard remains stuck. For example, if the entire network is in epoch 5 and a shard is still in epoch 2, at epoch change the other shards should keep more epochs in order to provide data to the shard with issues. => log displayed

Test reference (internal):
pruning-stuck-shard-log-1

The base branch was changed.

[AdoAdoAdo]

Can you please add for each manual testing scenario the following:

a) Prerequisites
b) Test steps
c) Expected results
d) Actual results

If there are parameters involved in testing what are the parameters boundaries and the expected results and actual results for testing inside boundaries, on boundaries and outside boundaries.

The base branch was changed.