Add CLP package launching to PR check workflow

[coderabbitai]

Background

Currently, CLP package launch issues (like the Python compatibility issue in #693) are only discovered after merging changes. Developers usually test on a single platform, such as Ubuntu Focal OR Ubuntu Jammy, and such compatibility issues are not easily discovered unless tests are performed on all platforms. Adding a package launch test to the PR check workflow would help catch these issues earlier in the development cycle.

Feature Request

Add a step to the PR check workflow that:

1. Builds the CLP package
2. Attempts to launch it in an environment similar to production
3. Verifies the launch was successful

This would help catch issues like:

• Python compatibility issues
• Missing dependencies
• Configuration problems
• Initialization failures

References

• Related issue: CLP package cannot start on Ubuntu Focal due to initialize-results-cache.py. #693

/cc @junhaoliao

[junhaoliao]

Alternatively, for the issue in #693 specifically, a linter rule can be added to disallow syntaxes that are only available in newer Python versions, if such rules exist.