Update current `eslint` rules to use resolved type information

[ImpregnableProgrammer]

At the moment, the ESLint rules as implemented rely on cursory selectors to identify certain constructs, which might be insufficient for identifying the same constructs defined via other valid means. For instance, the following selector is used to select choreographic variables:

const choreographySelector = `VariableDeclaration[kind = "const"] > VariableDeclarator[id.typeAnnotation.typeAnnotation.typeName.name = "Choreography"];

This will match choreographies declared as follows

const myChoreography: Choreography<Locations, [], []> = ...

But won't match the following

type MyType = Choreography<Locations, [], []>;
const myChoreography: MyType = ...

since the Choreography type is aliased with MyType. This problem can be fixed by rewriting the rules to use resolved type information provided by TypeScript's typechecker API.

[ImpregnableProgrammer]

This is being worked on in PR #37