Separate exclude patterns by root path in CLP task `lint:check-cpp-static-full` to avoid ambiguity.

[coderabbitai]

Problem Description

The exclude_patterns configuration in the lint:check-cpp-static-full task in CLP is confusing because it contains a mix of paths that belong to different root directories:

• Some patterns belong to the source file root path `clp/components/core/src/'
• Some patterns belong to the test root path `clp/components/core/tests/'

This creates confusion when similar relative paths exist in both the source and test directories, making it difficult to understand which files are actually being excluded. Internally, this also increases time complexity of ystdlib-py-find as there are unnecessary mix and match between wrong pairs of ROOT_PATH and EXCLUDE_PATTERNS.

Current State

As acknowledged, there's currently no good solution for this issue. The configuration works functionally but lacks clarity about which root path each exclude pattern applies to.

Context

This issue was identified during the refactoring of linting task configurations where relative paths were introduced to improve maintainability.

Backlinks

• Related PR: build(deps): Bump yscope-dev-utils to the newest version: clp#1126
• Original comment: build(deps): Bump yscope-dev-utils to the newest version: clp#1126 (comment)

Reported by: @Bill-hbrhbr