feat: run telemetry collection as a background process

[francinelucca]

Closes #143

Changelog

New

• Spawn detached child process in index.js to perform collection

Changed

• Moved index.js collection logic onto collect.js file
• Modified esbuild configuration to include two files: index.js (spawn process) and collect.js (collection)

Testing / reviewing

Try running collection from a "instrumented package" (for example, @carbon/react inside carbon-website) and confirm the process exists immediately and the temp log file is generated with correct metrics in the temp folder of machine.
CI='true' node [path-to-telemetry]/dist/index.js --config=telemetry.yml (remember to npm run build & npm run bundle the local telemetry package first)

[francinelucca]

@jdharvey-ibm I had to modify the build settings to output a dist folder instead of a single dist/out.js file since I need to build both index.js and collect.js, happy to talk through if there's a better way to do this.

[jdharvey-ibm]

We are okay with there being no new test coverage in this PR. The code is not worth the effort it would take to test it.

[sonarcloud]

Quality Gate failed

Failed conditions

0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud