refs 22658 Recognize history empty when seq_num_min is unknown

[EugenioCollado]

When an ack is made to the entire history in volatile, since the entries are directly deleted from the history, the check_acked_status method satisfies the condition min_low_mark >= get_seq_num_min() because seq_num_min is unknown as it is empty. This leads to changes being marked for deletion when, in reality, there are none, causing the try_remove method to fail thus causing prepare_change to drop the change because the history was full and changes could not be deleted.

Description

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• Any new/modified methods have been properly documented using Doxygen.
• Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
• Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• Changes are API compatible.
• New feature has been added to the versions.md file (if applicable).
• New feature has been documented/Current behavior is correctly described in the documentation.
• Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• If this is a critical bug fix, backports to the critical-only supported branches have been requested.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.