Adds status property to dpkg parsed packages

[fretb]

dpkg-query displays information about all packages on the system, meaning that removed (non-purged) packages that leave config-files are also in this list.

This makes it hard to identify actually installed
packages. By adding the db:Status-Status field to our package info hash, we have a lot more flexibility.

Slack discussion about this:
https://chefcommunity.slack.com/archives/C55FCUGBS/p1685438915205339.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

No Coverage information
66.7% Duplication

[Tensibai]

I kinda disagree with the non-breaking change, it does change what's reported (due to dpkg query change) so it should have a kinf of warning aroung the distro/dpkg version bringing the change and a proper Changelog entry IMHO.

Main question is: I wonder what happen for old 18.04 ubuntu without this dpkg-query update or if it is not relevant as 18.04 always had this behavior anyway.

Misread the changes, it is totally backward compatible, sounds good to me.

[jaymzh]

Nicely done. Thanks for doing this and the tests.

I'm approving, and I'll give throw it in the queue for anyone else to give any feedback or otherwise merge at the Monday meeting (I won't be there, still out of town), but in case they don't get to it, ping me and I'll merge it myself.