Typed config after npx ts-jest config:init

[wtho]

🚀 Feature Proposal

The initialized config should be typed. Everyone using this preset likes types.

Motivation

Everybody loves code completion

Example

Currently, after running npx ts-jest config:init, the following config is created:
jest.config.js:

module.exports = {
  preset: 'ts-jest',
  testEnvironment: 'node',
};

What I really want is either (stolen right from the jest docs)
jest.config.js:

/** @type {import('@jest/types').Config.InitialOptions} */
module.exports = {
  preset: 'ts-jest',
  testEnvironment: 'node',
};

Or alternatively (everyone using ts-jest also uses typescript, but this requires ts-node to be installed)
jest.config.ts:

import type { Config } from '@jest/types';

const config: Config = {
  preset: 'ts-jest',
  testEnvironment: 'node',
};

default export config;

I guess the comment type import is the way to go.