chore: bump kontrol version, and make output checks more robust

[mds1]

Some CI failures occurred due to silent failure of kontrol build (so CI should have failed earlier than it did). The newest version of kontrol has a fix for this, and we also update run-kontrl.sh to check for failure explicitly

[JuanCoRo]

I think the logic below the new changes is subsumed. So maybe consider removing these lines:

if [ "${results[0]}" -ne 0 ] && [ "${results[1]}" -ne 0 ]; then
  echo "Kontrol Build and Prove Failed"
  exit 1
elif [ "${results[0]}" -ne 0 ]; then
  echo "Kontrol Build Failed"
  exit 1
elif [ "${results[1]}" -ne 0 ]; then
  echo "Kontrol Prove Failed"
  exit 2
else

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 47.03%. Comparing base (3a97042) to head (301128f).
Report is 5 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #13697      +/-   ##
===========================================
- Coverage    47.23%   47.03%   -0.20%     
===========================================
  Files          953      953              
  Lines        79730    79730              
  Branches       766      766              
===========================================
- Hits         37657    37498     -159     
- Misses       39190    39394     +204     
+ Partials      2883     2838      -45     

Flag	Coverage Δ
cannon-go-tests-32	62.26% <ø> (ø)
cannon-go-tests-64	57.35% <ø> (ø)
contracts-bedrock-tests	87.90% <ø> (-2.60%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 27 files with indirect coverage changes

[mds1]

Nice catch @JuanCoRo, fixed in 301128f