Bug 2213325

Description of problem:
When displaying stopped pools, the encryption information
in the StoppedPools D-Bus property is unpacked in a manner that
unconditionally expects the structure that the value representing the
pools encryption status has if the
encryption information on the pool is consistent. This unpacking fails
with a ValueError and resulting stack trace if the encryption
information on the pool is inconsistent, as the structure  of the
value being unpacked in that
case is different.

Version-Release number of selected component (if applicable):
stratis-cli-3.5.2-1.el9

How reproducible:
100%

Steps to Reproduce:
1. Create a situation where encryption information on devices in a
single stopped Stratis pool is not consistent.

2. List the stopped pools: stratis pool list --stopped

3. Observe resulting stack trace with ValueError


Actual results:
Stack trace when listing stopped pools.

Expected results:
No stack trace when listing stopped pools.

Additional info:
There are various ways to generate the inconsistent encryption
information on devices within a stopped Stratis pool. Deterministic
techniques require using cryptsetup outside of Stratis to modify the
LUKS header on a device in a Stratis pool.