exclude .exp files from whitespace checks in scripts/git-checks.sh

[brmataptos]

Description

In git-checks.sh, exclude whitespace checks for .exp files, which are program-generated and can have any syntax.

Test Plan

Tested locally with various previous commits involving extra whitespaces. Verified that .exp files are excluded, but others are not.

Fixes

#12356

[trunk-io]

⏱️ 3h 59m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
rust-unit-tests	1h 2m	🟩 🟩
windows-build	29m	🟩 🟩
rust-smoke-tests	29m	🟩
execution-performance / single-node-performance	21m	🟩
forge-e2e-test / forge	19m	🟩
rust-images / rust-all	15m	🟩
rust-lints	15m	🟩 🟩
forge-compat-test / forge	13m	🟩
run-tests-main-branch	8m	🟩 🟩
check	8m	🟩 🟩
cli-e2e-tests / run-cli-tests	8m	🟩
general-lints	4m	🟩 🟩
check-dynamic-deps	4m	🟩 🟩
node-api-compatibility-tests / node-api-compatibility-tests	52s	🟩
semgrep/ci	47s	🟩 🟩
file_change_determinator	27s	🟩 🟩
file_change_determinator	21s	🟩 🟩
execution-performance / file_change_determinator	13s	🟩
file_change_determinator	10s	🟩
permission-check	9s	🟩 🟩
permission-check	6s	🟩 🟩
permission-check	5s	🟩 🟩
permission-check	4s	🟩 🟩
determine-docker-build-metadata	3s	🟩
permission-check	2s	🟩

🚨 2 jobs on the last run were significantly faster/slower than expected

Job	Duration	vs 7d avg	Delta
forge-e2e-test / forge	19m	14m
windows-build	12m	20m

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[github-actions]

✅ Forge suite compat success on aptos-node-v1.9.5 ==> 78aca67764d89a2160a03695668c762270401c51

Compatibility test results for aptos-node-v1.9.5 ==> 78aca67764d89a2160a03695668c762270401c51 (PR)
1. Check liveness of validators at old version: aptos-node-v1.9.5
compatibility::simple-validator-upgrade::liveness-check : committed: 5714 txn/s, latency: 5088 ms, (p50: 4800 ms, p90: 9300 ms, p99: 10200 ms), latency samples: 228580
2. Upgrading first Validator to new version: 78aca67764d89a2160a03695668c762270401c51
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 690 txn/s, latency: 33969 ms, (p50: 35600 ms, p90: 53200 ms, p99: 56000 ms), latency samples: 57280
3. Upgrading rest of first batch to new version: 78aca67764d89a2160a03695668c762270401c51
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 326 txn/s, submitted: 672 txn/s, expired: 346 txn/s, latency: 32542 ms, (p50: 40100 ms, p90: 48500 ms, p99: 57000 ms), latency samples: 23156
4. upgrading second batch to new version: 78aca67764d89a2160a03695668c762270401c51
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 2227 txn/s, latency: 13454 ms, (p50: 14300 ms, p90: 16000 ms, p99: 16900 ms), latency samples: 100220
5. check swarm health
Compatibility test for aptos-node-v1.9.5 ==> 78aca67764d89a2160a03695668c762270401c51 passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on 78aca67764d89a2160a03695668c762270401c51

two traffics test: inner traffic : committed: 7405 txn/s, latency: 5284 ms, (p50: 5100 ms, p90: 6300 ms, p99: 13500 ms), latency samples: 3206540
two traffics test : committed: 100 txn/s, latency: 1989 ms, (p50: 1800 ms, p90: 2100 ms, p99: 8800 ms), latency samples: 1800
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.232, avg: 0.202", "QsPosToProposal: max: 0.367, avg: 0.287", "ConsensusProposalToOrdered: max: 0.480, avg: 0.444", "ConsensusOrderedToCommit: max: 0.332, avg: 0.302", "ConsensusProposalToCommit: max: 0.778, avg: 0.746"]
Max round gap was 1 [limit 4] at version 2535. Max no progress secs was 4.200217 [limit 15] at version 1951370.
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking