fix: check for body type before parsePush execution

[jescalada]

Fixes #1509.

[netlify]

✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.

Name	Link
🔨 Latest commit	aa7c42c
🔍 Latest deploy log	https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/69e97d10f4e5d10008363e5c

[codecov]

Codecov Report

❌ Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.18%. Comparing base (6981427) to head (aa7c42c).
⚠️ Report is 7 commits behind head on main.

Files with missing lines	Patch %	Lines
src/proxy/processors/push-action/parsePush.ts	33.33%	2 Missing ⚠️

❌ Your patch check has failed because the patch coverage (33.33%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1511      +/-   ##
==========================================
- Coverage   90.21%   90.18%   -0.04%     
==========================================
  Files          69       69              
  Lines        5511     5514       +3     
  Branches      944      946       +2     
==========================================
+ Hits         4972     4973       +1     
- Misses        521      523       +2     
  Partials       18       18              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jescalada]

This bit had to be removed in order to fix the "unpinned dependency" alert https://github.com/finos/git-proxy/security/code-scanning/113. I think this shouldn't cause issues since the published package wouldn't include the peer dep (finos/git-proxy) - unless I'm missing something 🤔

Pinging @coopernetes just in case!

[kriswest]

doesn't it just need switching to npm ci?

[kriswest]

Please update the PR title as scope is beyond whaats described, otherwise LGTM