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

• [X] Bug fix (non-breaking change which fixes an issue)
• [X] 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:

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

[sonarcloud[bot]]

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.