[Telemetry] Refactor telemetry with build report

[yoannmoinet]

Warning

To merge into #92

What and why?

Now that we have an universal build-report, we can refactor the telemetry module to also be universal for the most part.

How?

It's a large refactor of the telemetry module.
Removing most of the esbuild/webpack specificities.
Only remaining ones are about the tracing and reporting of plugins/loaders.

Most of the main processes have been streamlined

• metrics aggregation
• text report output
• default configuration

A lot of tests added/redone:

• Added a .toBeWithinRange helper for Jest.
• Added the ./setupTests.ts file to inject the helpers and block any network request with nock.
• More .each to reduce footprint of some tests.

It also introduces some configuration changes:

• endPoint has moved in telemetry` configuration.
• We also added enbaledTracing to run the tracing and reporting of plugins/loaders for webpack and esbuild. It is false by default, as it has a somewhat heavy impact on the builds.
• telemetry.output has been simplified, we only write two files now.
• The text output of the telemetry module will follow the logLevel configuration on the info channel.

const config = {
    plugins: [
        datadogEsbuildPlugin({
            auth: {
-             endPoint: 'app.datadoghq.com',
            },
            telemetry: {
+             endPoint: 'app.datadoghq.com',
+             enableTracing: false,
              output?: boolean
                  | string
                  | {
                      destination: string;
                      timings?: boolean;
-                     dependencies?: boolean;
-                     bundler?: boolean;
                      metrics?: boolean;
-                     logs?: boolean;
                  };
            },
        }),
    ]
};

Update of the text report:

Fixes #79