Fix compilation error on master

[Shadow-Devil]

Purpose

Fix the compilation error introduced in #42854.
There, the JsonParser object was used, which was removed with #42945

Check List

• Read the Contributing Guide
• Updated Change Log
• Checked Tooling Support (#)
• Added necessary tests
  • Unit Tests
  • Spec Conformance Tests
  • Integration Tests
  • Ballerina By Example Tests
• Increased Test Coverage
• Added necessary documentation
  • API documentation
  • Module documentation in Module.md files
  • Ballerina By Examples

[Shadow-Devil]

@gimantha Could you please review and merge this PR before reviewing any of my other PRs?
I fixed the compilation error introduced in #42854
and also noticed that in #43067 I made a mistake for defining the output zip file.
This is now fixed, sorry for the inconvenience.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.50%. Comparing base (0477a4a) to head (1622a6f).
Report is 64 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #43394      +/-   ##
============================================
- Coverage     77.50%   77.50%   -0.01%     
- Complexity    58581    58583       +2     
============================================
  Files          3438     3438              
  Lines        219214   219215       +1     
  Branches      28919    28919              
============================================
  Hits         169910   169910              
- Misses        39890    39892       +2     
+ Partials       9414     9413       -1     

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

[gimantha]

@gimantha Could you please review and merge this PR before reviewing any of my other PRs? I fixed the compilation error introduced in #42854 and also noticed that in #43067 I made a mistake for defining the output zip file. This is now fixed, sorry for the inconvenience.

Sure.. but wondering where it was broken. I cannot see that the build is failing in the pointed PR. is it a regression issue not reflected in our tests?

[Shadow-Devil]

There should have been a merge conflict in #42854 but this wasn't detected by git. The pipeline ran with the previous version of master, where the parser variable was still defined.

[Shadow-Devil]

In summary: #42854 used a variable that was removed in #42945, but since the pipeline was running with the state of the branch, where the variable still existed there was no failure. This could have been prevented by either merging master into #42854 or rebasing it onto master.
The other issue with #43067 was not noticed because the successful build steps were cached. Once this cache expired and it was executed again it threw the build failure.