## Summary
This replaces the `console.log` we have with `ToolingLog` which is what the e2e tests want to use. Right now they're producing a lot of `console.log` debugging information and noise which we don't want. Instead we want to use the standard tool logging that e2e has for the FTR tests.
The two most important files with changes are:
* x-pack/test/detection_engine_api_integration/utils.ts
* x-pack/test/lists_api_integration/utils.ts
From there everything else is just a repeating pattern of:
```ts
const log = getService('log');
```
And then pushing the log into the utilities:
such as:
```ts
await deleteListsIndex(supertest, log);
```
For reviewers, if you want to, checkout this branch and just ensure I didn't miss a `console.log` statement within the e2e tests anywhere. Also double check I did the correct `log.debug` vs `log.error` or if you think I misinterpreted one, point it out. I use `log.debug` where I have retries and then I use `log.error` where I thought it would be most useful to call out a very probable or unexpected statement happening when the tests begin to go sideways or have issues.
### Checklist
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
f7761d9fca