src: add setTitle() as alternative to direct assignment

[JonathanLopes404]

Implement process.setTitle(title) as a new function-based API for setting the process title, complementing the existing process.title property assignment pattern

Fixes: #62797

[nodejs-github-bot]

Review requested:

• @nodejs/startup

[addaleax]

Why does this introduce a new native method? Adding the new API is fine, but it should just trigger the same code paths.

[JonathanLopes404]

@addaleax Updated in latest commit: setTitle now reuses the existing process.title path (removed native method). Could you please take another look?

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/72786/

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.70%. Comparing base (bee1087) to head (c16ebdd).
⚠️ Report is 23 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #62804      +/-   ##
==========================================
+ Coverage   89.68%   89.70%   +0.01%     
==========================================
  Files         706      706              
  Lines      218191   218237      +46     
  Branches    41746    41768      +22     
==========================================
+ Hits       195691   195773      +82     
+ Misses      14427    14373      -54     
- Partials     8073     8091      +18     

Files with missing lines	Coverage Δ
...l/bootstrap/switches/does_not_own_process_state.js	100.00% <100.00%> (ø)
...ernal/bootstrap/switches/does_own_process_state.js	95.33% <100.00%> (+0.19%)	⬆️

... and 66 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[silverwind]

Would add a reference on bottom of the process.title docs to point to the new alternative.

[ljharb]

I'm confused why an alias for x => { process.title = x } is helpful - if it were an entirely new method, such that one could eventually deprecate the assignment form, that'd be one thing.

Separately, is it expected that if i Object.defineProperty(process, 'title', { writable: false, configurable: false }), setTitle will throw?