[PreTest]The checksum check of the three-party dependencies

[vinayakjaas]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #394 ",.):

• N
• Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

[vinayakjaas]

Hey @Peefy ,@zong-zhe,@AkashKumar7902 I've opened a pull request that includes detailed documentation regarding the checksum check for third-party dependencies. I've put significant effort into designing this, but I would greatly appreciate your review and any necessary modifications.
Please note that the implementation may not be complete yet, as I am still exploring codebase to find some additional approaches to address the issue. I’m happy to make further changes based on your feedback.

[zong-zhe]

Hi @vinayakjaas 😃

Split the different jobs into their own PR and associate them with the corresponding issues.

[vinayakjaas]

Hey @zong-zhe, I have separated both pull requests as requested. Could you please go through and review them

[Peefy]

@zong-zhe Could you help review it?

[coveralls]

Pull Request Test Coverage Report for Build 10160038561

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 39.674%

---

Totals
Change from base Build 10137817925:	0.0%
Covered Lines:	3066
Relevant Lines:	7728

---

💛 - Coveralls

[vinayakjaas]

Hi @zong-zhe , please review this PR If you find any modifications are needed, please let me know, and I'll be happy to make the necessary changes.

[Peefy]

cc @zong-zhe Could you help review it?

[zong-zhe]

Hi @vinayakjaas 😄

Try to add a separate module Checker to complete this part of the work, including three-party dependency name check, version number check and sum check.