aws_lambda_nodejs: specify outDir when using preCompilation

### Describe the feature

When bundling an AWS Lambda using the `preCompilation` option, JS files are emitted in the same location as the TS files.
When working with a lot of TS files, it's very annoying to get dozen of JS files generated.
We should be able to define an output directory.
Pre-compilation forces the `outDir` option to be `./` which totally overrides the value defined in the `tsconfig.json`.

### Use Case

When doing a `cdk synth` or `cdk build` when the `preCompilation` option is used, it's frustrating to get JS files generated in the same location as the TS files.
I would like to specify an output directory for the JS files but the `outDir` option from the `tsconfig.json` is ignored.

### Proposed Solution

The function `getTsconfigCompilerOptions` force the `outDir` to `./`.
```
const options: Record = {
...compilerOptions,
// Overrides
incremental: false,
// Intentionally Setting rootDir and outDir, so that the compiled js file always end up next to .ts file.
rootDir: './',
outDir: './',
};
```
If the `outDir` option is defined in the `tsconfig.json`, it should be taken into account.
esbuild will not know where is the generated JS file but we may be able to specify the path using the `esbuildArgs` option.

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [x] This feature might incur a breaking change

### CDK version used

2.20.0

### Environment details (OS name and version, etc.)

macOS 12.2.1

Start by reading getTsconfigCompilerOptions and the preCompilation path described in the issue. Check how tsconfig.json compilerOptions and esbuildArgs determine the generated JavaScript location. Done means a configured outDir is respected without leaving compiled files beside the TypeScript sources, with the resulting esbuild path handled.

Written by the indexing model from the issue text.