feat: Add sub config for TypeScript projects

[susnux]

This adds a sub-config for typescript projects, e.g. we could use it within our libraries or for users which use TypeScript for app development (vue + ts is pretty common nowadays).

[skjnldsv]

Can't we just support typescript out of the box?
Surely there is a way to define different rules for ts and js files, no?

[susnux]

Can't we just support typescript out of the box? Surely there is a way to define different rules for ts and js files, no?

@skjnldsv Good point! I changed it to simply use overrides.

[skjnldsv]

Could we maybe disable jsdoc for ts files?

[susnux]

Could we maybe disable jsdoc for ts files?

This is the same behavior as for js file, why should we treat ts file differently regarding documentation?
One reason I see is the built in type information, thats why I disabled jsdoc/require-param-type.
(I am just curious)

Edit:
For exported functions I think warning on missing parameter documentation is good,
but if you are talking about the now required docs of helper callbacks, then you can circumvent this.
From the linked pull request

await new Promise((resolve, reject): any => docker.pull(SERVER_IMAGE, (_err, stream) => {
	some(onFinished);

	/**
	 *
	 * @param err
	 * @param output
	 */
	function onFinished(err, output) {
	// ...

This can be rewritten to prevent es-lint complaing about missing documentation of onFinished like this:

await new Promise((resolve, reject): any => docker.pull(SERVER_IMAGE, (_err, stream) => {
	const onFinished = (err, output) => {
	}

	some(onFinished);

[skjnldsv]

For exported functions I think warning on missing parameter documentation is good,

Ah right, typing requirements is bad, but param documentation is still quite good to have! 👍

[skjnldsv]

@susnux why disabling this rule btw?
If we cannot resolve, maybe it's bad?