[Chore](thirdparty) add crc32c-1.1.2 to thirdparty

[BiteTheDDDDt]

What problem does this PR solve?

doris have crc32c from rocksdb now, but it has poorly performance than google/crc32c.

66663538 rows int
crc32c-rocksdb 684.879ms
crc32c-google 206.360ms

66663538 rows varchar
crc32c-rocksdb 1sec368ms
crc32c-google 391.290ms

This pull request adds support for the crc32c third-party dependency to the build environment. The changes include updating the changelog, adding build logic, and configuring the necessary variables to download and build crc32c.

Third-party dependency integration:

• Added crc32c-1.1.2 to the list of third-party dependencies in the changelog (thirdparty/CHANGELOG.md).
• Added crc32c to the default package build list in build-thirdparty.sh to ensure it is built by default.
• Implemented the build_crc32c() function in build-thirdparty.sh to handle the build and installation process for crc32c.

Build configuration updates:

• Defined download URL, archive name, source directory, and MD5 checksum for crc32c in vars.sh.
• Added CRC32C to the TP_ARCHIVES array in vars.sh so it is included in the set of managed third-party archives.

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[Thearas]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[BiteTheDDDDt]

run buildall

[HappenLee]

LGTM

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.