fix(typegraph): send rpc message in chunks in the TS typegraph client

[Natoandro]

• Send the JSON-RPC message is chunks in the TypeScript typegraph client to prevent reaching the line size limit for stdout. Note: we could not reproduce the issue locally as it only occurs when using the published package for Node.js.
• Use JSON-RPC notification for logging and report from the typegraph clients.
• Other changes:
  • Use relative paths for static task sources in the CLI;
  • Fix TODO in meta gen: pass the working directory on the working_dir param of SerializeActionGenerator::new.

Migration notes

N/A

---

• The change comes with new or modified tests
• Hard-to-understand functions have explanatory comments
• End-user documentation is updated to reflect the change

[codecov]

Codecov Report

Attention: Patch coverage is 59.37500% with 13 lines in your changes missing coverage. Please review.

Project coverage is 77.46%. Comparing base (18a13d6) to head (82e98be).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/typegraph/deno/src/io.ts	59.37%	13 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #904      +/-   ##
==========================================
- Coverage   77.46%   77.46%   -0.01%     
==========================================
  Files         149      149              
  Lines       18244    18263      +19     
  Branches     1785     1785              
==========================================
+ Hits        14133    14147      +14     
- Misses       4088     4093       +5     
  Partials       23       23              

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

[michael-0acf4]

Since the message length returns the number of code units not the characters. With string slice there is still a risk of cutting in the middle of a character.
I suggest using Array.from(message) to get an actual iterator to the characters then perform slice on that. That would also mean additional fixes around the actual total length though.. but if it's about sending raw bytes it should be fine I guess.

const text = "Hello👍";
console.log(text.length); // 7 not 6
console.log(text.slice(0, 6));
console.log(Array.from(text).slice(0, 6). join(""));

[Natoandro]

@michael-0acf4
Good point... Each entry is parsed as a string on the rust side, so UTF validation might fail...
Unless the implementation follows the well-formed JSON.stringify implementation; which we can assume...
Because the message should be a valid JSON...