[chore] add license compliance checker for Conan dependencies

[yangzhg]

What problem does this PR solve?

Issue Number: close #64

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🚀 Performance improvement (optimization)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
• 🔨 Refactoring (no logic changes)
• 🔧 Build/CI or Infrastructure changes
• 📝 Documentation only

Description

This PR introduces a Python-based tool to ensure our project's dependencies remain compliant with the Apache Software Foundation (ASF) licensing requirements.

Key Changes

• Dependency Flattening: The script traverses the full Conan dependency graph to ensure no transitive dependencies are missed.
• License Validation: Checks each dependency against the ASF 3rd Party License Policy.
• Reporting: Provides a clear console output showing:
  • ✅ Approved licenses (Category A/B).
  • ❌ Prohibited licenses (Category X).
  • ⚠️ Unknown/Missing license metadata.

Performance Impact

• No Impact: This change does not affect the critical path (e.g., build system, doc, error handling).

• Positive Impact: I have run benchmarks.

  Click to view Benchmark Results

  Paste your google-benchmark or TPC-H results here.
  Before: 10.5s
  After:   8.2s  (+20%)
  

• Negative Impact: Explained below (e.g., trade-off for correctness).

Release Note

Please describe the changes in this PR

Release Note:

Release Note:
 [chore]: add license compliance checker for Conan dependencies
    - Implement a script to flatten Conan dependency tree.
    - Add logic to verify dependency licenses against ASF (Apache Software Foundation) compatibility.
    - Generate a summary report of compliant and non-compliant packages.

Checklist (For Author)

• I have added/updated unit tests (ctest).
• I have verified the code with local build (Release/Debug).
• I have run clang-format / linters.
• (Optional) I have run Sanitizers (ASAN/TSAN) locally for complex C++ changes.
• No need to test or manual test.

Breaking Changes

• No

• Yes (Description: ...)

  Click to view Breaking Changes

  Breaking Changes:
  - Description of the breaking change.
  - Possible solutions or workarounds.
  - Any other relevant information.