fix: validate plan and result calldata lengths

[JayWhite2357]

Please be sure to look over the pull request guidelines here: https://github.com/spaceandtimelabs/sxt-proof-of-sql/blob/main/CONTRIBUTING.md#submit-pr.

Please go through the following checklist

• The PR title and commit messages adhere to guidelines here: https://github.com/spaceandtimelabs/sxt-proof-of-sql/blob/main/CONTRIBUTING.md. In particular ! is used if and only if at least one breaking change has been introduced.
• I have run the ci check script with source scripts/run_ci_checks.sh.
• I have run the clean commit check script with source scripts/check_commits.sh, and the commit history is certified to follow clean commit guidelines as described here: https://github.com/spaceandtimelabs/sxt-proof-of-sql/blob/main/COMMIT_GUIDELINES.md
• The latest changes from main have been incorporated to this PR by simple rebase if possible, if not, then conflicts are resolved appropriately.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.13%. Comparing base (fa580de) to head (82d4e2e).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #749   +/-   ##
=======================================
  Coverage   96.13%   96.13%           
=======================================
  Files         331      331           
  Lines       58592    58592           
=======================================
  Hits        56325    56325           
  Misses       2267     2267           

☔ 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.