Fix the bug that AgentExec didn't return right pid number

[Jlan45]

No description provided.

[luthermonson]

welp looks like i need an alpha10 now lol.. thanks for the PR and nice catch

[codecov]

Codecov Report

Merging #98 (f3f470a) into main (fac5f8a) will decrease coverage by 0.02%.
Report is 1 commits behind head on main.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #98      +/-   ##
==========================================
- Coverage   26.13%   26.12%   -0.02%     
==========================================
  Files          15       15              
  Lines        1714     1715       +1     
==========================================
  Hits          448      448              
- Misses       1246     1247       +1     
  Partials       20       20              

Files	Coverage Δ
virtual_machine.go	2.81% <0.00%> (-0.01%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Jlan45]

Bug: AgentExec always return pid 0 with an error
Reasons: client.Post will finally call client.handleResponse to process the returned json data. At the end, if there is a data key to parse the json data, it will directly bind the data in the data to the value we initially passed.In other functions, we pass in a structure. As long as the json data is parsed normally, we can get a complete return. However, in the AgentExec function, the pid we pass in is an int type. Obviously, json cannot bind the data, resulting in a json deserialization error, which leads to no effective pid return.
Fix:By adding a temporary map object to parse the json data, and then take out the value of the pid and return it.