Better support for dependencies shared between multiple projects

[coderabbitai]

Problem

When multiple projects within a single repository (e.g., spider and clp) call install-deps-and-generate-settings with:

• The same CMAKE_SETTINGS_DIR
• Different CMAKE_SETTINGS_FILE values (e.g., all-core.cmake and all-spider.cmake)

The current implementation handles shared dependencies correctly, but the generated CMake settings files may include unnecessary dependencies from other projects.

Context

This issue was identified during the refactoring of dependency tasks in y-scope/clp#1377. The PR works around the limitation by splitting dependency tasks into separate modular files, but a proper solution in dev-utils would provide better support for this use case.

Requested Enhancement

Add better support for scenarios where multiple projects in the same repository share dependencies and need to call install-deps-and-generate-settings multiple times with different output files.

References

• PR discussion: refactor(taskfile): Split main dependency Taskfile into category-specific modules; Migrate antlr-runtime and utfcpp to use utils:install-remote-cmake-lib. clp#1377 (comment)
• Original PR introducing spider deps: feat(clp-package): Add Spider and its dependencies to the build. clp#1318
• Follow-up mitigation: fix(taskfile): Make deps:core and deps:spider-dep write into different top-level CMake configuration files (fixes #1330). clp#1331
• Requested by: @sitaowang1998

[sitaowang1998]

The major problem is not unnecessary files. This is only a good-to-have feature.
The biggest problem is the install-deps-and-generate-settings removes and recreates the CMAKE_SETTING_DIR. This leads to concurrency issue when more than one tasks execute this task.
Another good-to-have feature is to creates directory of CMAKE_SETTING_FILE in install-deps-and-generate-settings, so we can write the combined cmake setting files into different folders.