Description of problem:
A new Github issue came in where a user was asking about changing the "indexSparse" setting in /etc/vdoconf.yml (which is unsupported, but not impossible) to change the size of their index.  I decided to try this to see what effect this change had on the volume.  I created a fresh VDO volume, wrote some data, stopped the volume, edited the config file from a 0.25/dense index to now say it is 0.25/sparse, and then started the volume.  Everything came up fine, and deduplication was working.  When I run `vdo status --verbose`, the output indicates that the index is Sparse, which is not the case.  If I run `vdodumpconfig` against my backing device, the correct setting is displayed.

This bug is intended to adjust the behavior of VDO Manager to properly report configurations from `vdodumpconfig` when that is available, and only report the contents of /etc/vdoconf.yml when the live-data is not available.  There may be other values that are also affected by this.  Those should be adjusted as well if they are discovered.

Version-Release number of selected component (if applicable):
vdo-6.2.2.33-12.el8

How reproducible:
100%

Steps to Reproduce:
1. Create a VDO volume with default index settings (0.25/dense) `vdo create --name vdo0 --device /dev/loop0 --indexMem 0.25 --sparseIndex disabled`
2. Observe index setting `vdo status --verbose | grep 'Index sparse'`
3. Stop VDO volume `vdo stop --name vdo0`
4. Edit /etc/vdoconf.yml, changing "indexSparse: disabled" to "indexSparse: enabled"
5. Start VDO volume `vdo start --name vdo0`
6. Observe incorrect index setting `vdo status --verbose | grep 'Index sparse'`
7. Observe correct index setting `vdodumpconfig /dev/loop0 | grep sparse:`

Actual results:
[root@host-10-0-136-207 ~]# vdo status --verbose | grep 'Index sparse'
    Index sparse: enabled

Expected results:
[root@host-10-0-136-207 ~]# vdo status --verbose | grep 'Index sparse'
    Index sparse: disabled

Additional info:
This has no effect on the operation of the VDO volume, but should someone go in and modify this file, it can lead to confusion about its configuration.