cscp: update binary hash

[AlexMnrs]

Summary

• Update the cscp manifest hash for the current binary.7z download.

Why

The existing hash no longer matches the upstream archive reported in #41.

Validation

• Downloaded http://takeda-toshiya.my.coocan.jp/common/binary.7z
• Confirmed first bytes: 37 7A BC AF 27 1C 00 04
• Confirmed SHA256: 9c0ecebc187d25b7c841f222b2057625ff6286abaf954adc85fe15cd8f778ff5
• Parsed bucket/c/cscp.json as JSON
• Ran git diff --check

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[AlexMnrs]

I checked the AppVeyor failure for this PR. The changed manifest validates successfully:\n\n- Manifest validates against the schema: bucket/c/cscp.json ✅\n\nThe failing AppVeyor tests appear to be repo-wide style checks on unrelated existing files, specifically missing final newlines and trailing whitespace in many manifests outside this PR's diff. I left the PR as draft while that external CI state is red, but the cscp hash change itself was validated locally and by AppVeyor's manifest schema test.