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)
• 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

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

Further comments

[codecov]

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.

❗ 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	Coverage Δ
crates/core/plugin_sm/src/plugin_manager.rs	55.1% <100.0%> (-11.0%)	⬇️
.../tedge_config/src/tedge_config_cli/tedge_config.rs	76.5% <77.7%> (-0.5%)	⬇️
crates/core/tedge_api/src/error.rs	0.0% <0.0%> (ø)
crates/core/plugin_sm/src/plugin.rs	13.3% <12.9%> (+<0.1%)	⬆️

... and 45 files with indirect coverage changes

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
435	0	3	435	100	0s

[reubenmiller]

We'll have to do the settings in a non breaking way as the old apt.name and apt.maintainer (inclusive) filters still need to be accepted (otherwise it will break everyone's existing config, and it will be in violation of the semver versioning).

We can introduce new settings but we need to then map the old settings to the new ones.

Also I'm not sure I fully understand the decision around the tedge-apt-plugin flag choice, as it stands the user can't use inclusive and exclusive filters via the cli...I would have expected something like "--inclusive-name" and "--exclusive-name" flags. The flag renaming is less important here as this was only ever used for adhoc validation an shouldn't break anyone's existing setup

[gligorisaev]

Test

• filter_packages_list_output_with_exclude_pattern.robot
  Appears to be well-structured, covering a range of scenarios, and designed with maintainability and reliability in mind. Provides solid foundation for testing package filtering functionality
• tests/RobotFramework/tests/plugin_apt/filter_packages_list_output_with_include_pattern.robot
  Changes should be acurate enought to check the functionality properly
• tests/RobotFramework/tests/tedge/call_tedge_config_list.robot
  Effectively tests the setting and unsetting of configuration values for apt name and maintainer.

[didier-wenzek]

Approved - with a suggestion

.unwrap_or_default is safe, no blockers

[Bravo555]

Assuming the test cases are sufficient and correct, the implementation is correct.

[reubenmiller]

Looks great. I experimented with the filters on a Yocto device and the combination of filters was able to reduce the list from 2000 to 160, perfect.