Disable failing custom lint rules

[sandersn]

Not sure why they fail yet -- I'll investigate on Friday.

Some others may fail too, but these two are the worst offenders.

[IvanGoncharov]

@sandersn @andrewbranch I investigated it since we experienced this problem in graphql-js repo:
https://github.com/graphql/graphql-js/blob/7a327a6e2045e75c577be924694e6642d3e28e14/src/tslint.json#L6-L7

It happens because dtslint and tslint use different typescript packages you can check this with npm ls typescript here is our output:

[email protected] /Users/ivang/dev/graphql-js
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]  deduped
│ └── [email protected]
└── [email protected]

So tslint produce AST with an older version of typescript and pass it to the dtslint custom rules that check kind values against enum from a newer typescript package, for example:

dtslint/src/rules/voidReturnRule.ts

Lines 59 to 68 in 5a62414

	case ts.SyntaxKind.ArrowFunction:
	case ts.SyntaxKind.CallSignature:
	case ts.SyntaxKind.FunctionDeclaration:
	case ts.SyntaxKind.FunctionExpression:
	case ts.SyntaxKind.FunctionType:
	case ts.SyntaxKind.MethodDeclaration:
	case ts.SyntaxKind.MethodSignature:
	return true;
	default:
	return false;

[IvanGoncharov]

Also, it looks like a long-standing issue and it was reported in #281

[ExE-Boss]

I’ve implemented a workaround in DefinitelyTyped/DefinitelyTyped#45148.