feat(sm-plugin): filter packages output list with exclude/include pattern

[Ruadhri17]

Proposed changes

This PR introduce two new tedge configs: software.plugin.include and software.plugin.exclude. This allows to filter packages list output in sm-plugin using include pattern and exclude pattern. When both patterns are provided in config, include pattern takes precedence over exclude pattern.

Types of changes

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• [ ] Documentation Update (if none of the other choices apply)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

2848

Checklist

• [x] I have read the CONTRIBUTING doc
• [x] I have signed the CLA (in all commits with git commit -s)
• [x] I ran cargo fmt as mentioned in CODING_GUIDELINES
• [x] I used cargo clippy as mentioned in CODING_GUIDELINES
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] I have added necessary documentation (if appropriate)

Further comments

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 27.65957% with 34 lines in your changes are missing coverage. Please review.

Project coverage is 78.1%. Comparing base (33e6890) to head (eb60c35). Report is 51 commits behind head on main.

:exclamation: Current head eb60c35 differs from pull request most recent head 40e1cfe

Please upload reports for the commit 40e1cfe to get more accurate results.

Additional details and impacted files

| [Files](https://app.codecov.io/gh/thin-edge/thin-edge.io/pull/2869?dropdown=coverage&src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=thin-edge) | Coverage Δ | | |---|---|---| | [crates/core/plugin\_sm/src/plugin\_manager.rs](https://app.codecov.io/gh/thin-edge/thin-edge.io/pull/2869?src=pr&el=tree&filepath=crates%2Fcore%2Fplugin_sm%2Fsrc%2Fplugin_manager.rs&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=thin-edge#diff-Y3JhdGVzL2NvcmUvcGx1Z2luX3NtL3NyYy9wbHVnaW5fbWFuYWdlci5ycw==) | `55.1% <100.0%> (-11.0%)` | :arrow_down: | | [.../tedge\_config/src/tedge\_config\_cli/tedge\_config.rs](https://app.codecov.io/gh/thin-edge/thin-edge.io/pull/2869?src=pr&el=tree&filepath=crates%2Fcommon%2Ftedge_config%2Fsrc%2Ftedge_config_cli%2Ftedge_config.rs&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=thin-edge#diff-Y3JhdGVzL2NvbW1vbi90ZWRnZV9jb25maWcvc3JjL3RlZGdlX2NvbmZpZ19jbGkvdGVkZ2VfY29uZmlnLnJz) | `76.5% <77.7%> (-0.5%)` | :arrow_down: | | [crates/core/tedge\_api/src/error.rs](https://app.codecov.io/gh/thin-edge/thin-edge.io/pull/2869?src=pr&el=tree&filepath=crates%2Fcore%2Ftedge_api%2Fsrc%2Ferror.rs&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=thin-edge#diff-Y3JhdGVzL2NvcmUvdGVkZ2VfYXBpL3NyYy9lcnJvci5ycw==) | `0.0% <0.0%> (ø)` | | | [crates/core/plugin\_sm/src/plugin.rs](https://app.codecov.io/gh/thin-edge/thin-edge.io/pull/2869?src=pr&el=tree&filepath=crates%2Fcore%2Fplugin_sm%2Fsrc%2Fplugin.rs&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=thin-edge#diff-Y3JhdGVzL2NvcmUvcGx1Z2luX3NtL3NyYy9wbHVnaW4ucnM=) | `13.3% <12.9%> (+<0.1%)` | :arrow_up: | ... and [45 files with indirect coverage changes](https://app.codecov.io/gh/thin-edge/thin-edge.io/pull/2869/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=thin-edge)

[github-actions[bot]]

Robot Results

:white_check_mark: Passed	:x: Failed	:next_track_button: Skipped	Total	Pass %	:stopwatch: Duration
435	0	3	435	100	0s

[didier-wenzek]

After discussion with @reubenmiller, we concluded that:

• the current behavior of this PR is what we expect (i.e. list a package if explicitly included or not explicitly excluded)
• except this should be done for all the software plugins and not just for apt
• hence the filters apply only to the package names and not to the maintainers (the latter being only available at the apt plugin level).

Hence:

• the current work as to be reverted as no changes are expected for tedge-apt-plugin :-(
• two new tedge config setting have to be added: software.plugin.include and software.plugin.exclude
• these two optional regex patterns are to be used by ExternalPluginCommand::list()
• the patterns apply to the package names
• if both are provided, the logic is to keep a package if its name matches the software.plugin.include regex or doesn't match the software.plugin.exclude. The logic is that the primary usage will be to exclude packages (say all libs and kernel modules) and only then add some exceptions (say to include the libc).
• if only software.plugin.include is provided, keep a package if its name matches
• if only software.plugin.exclude is provided, keep a package if its name doesn't match
• by the way, @Ruadhri17 , you were correct: it might be simpler to keep separate each case
• finally this has to combined with the current logic for keeping at most software.plugin.max_packages packages.