Add Process object so as to allow process.env

[randomboi404]

This Pull Request fixes/closes #4492.

It changes the following:

1. Ability to access ENV variables passed into boa:

Example code

const api_key = process.env.API_KEY
API_KEY=xxxxx boa -m app.js

2. Allows future addition of other process object methods of node js.

[github-actions]

Test262 conformance changes

Test result	main count	PR count	difference
Total	52,598	52,598	0
Passed	49,420	49,421	+1
Ignored	2,134	2,134	0
Failed	1,044	1,043	-1
Panics	0	0	0
Conformance	93.96%	93.96%	+0.00%

Fixed tests (1):

test/staging/Temporal/v8/instant-to-json.js (previously Failed)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.49%. Comparing base (6ddc2b4) to head (77c459c).
⚠️ Report is 644 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4597      +/-   ##
==========================================
+ Coverage   47.24%   56.49%   +9.25%     
==========================================
  Files         476      547      +71     
  Lines       46892    60060   +13168     
==========================================
+ Hits        22154    33933   +11779     
- Misses      24738    26127    +1389     

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

🚀 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.

[hansl]

2 non-blocking nits for now. If you want to merge without addressing that's fine we can do it in a follow up PR.

[randomboi404]

That makes sense.

Regarding the new TestAction::harness() since console tests haven't been migrated yet, I think it's better to let process be consistent with it and do a follow up once test harness is adopted more broadly.

Regarding it being enabled by default, I think we should let it be enabled for now and if in case we strictly don't want it enabled as it's a node api, we'll do a follow up to make it not being enabled by default.

[nekevss]

I'd second having the Process extension not on by default.

I think this is a super cool extension to have as an option, but since process is not based on a web standard, we should have it be an opt in extension and not opt out.

[randomboi404]

Done! I've made it optional.

[nekevss]

Thanks! 😄

The feature flag approach looks good to me!

[jedel1043]

Thank you for the contribution! I have a couple of questions about the implementation

[jedel1043]

Looks good! Thank you!