Colors codemod types

[martimalek]

What:

Make the colors-to-css-vars codemod take into account Colors being used as a type instead of as a constant
​
Why:

When Colors was used as a type the codemod was not transforming it, which made the resulting file invalid

import { Colors } from '@freenow/wave';

export interface AnotherInterface { color?: Colors }

should be transformed to

import { ReadCssColorVariable } from '@freenow/wave';

// eslint-disable-next-line @typescript-eslint/ban-types you can remove this comment and only use the `ReadCssColorVariable` type after changing the bare colors to `getSemanticValue`
export interface AnotherInterface { color?: ReadCssColorVariable | (string & {}) }

​
How:

• In colors-to-css-vars codemod, find usages of Colors as a type, replace them for the ReadCssColorVariable type and add it as an import
• I've also added an early return checking if Colors is imported, so that in case it isn't we stop executing the codemod
• Since the codemod adds an import for ReadCssColorVariable, I've exported the type from a essentials/index.ts

Checklist:

• Add eslint-disable comment to Colors type replacement so it doesn't break linting
• Ready to be merged

Closes #394

[martimalek]

I've created the colors-codemod-add-eslint-comment branch with some tries on how to add the eslint disable comment to usages of Colors as a type.

I'll have to park this for a bit due to other priorities and I've created that branch in case we want to move forward with the current solution without the comments.

EDIT: I've finally had some time to implement this, the solution is in this branch/PR, so I've deleted the other one

[nlopin]

Nice! I've added the type cleanup step to the migration guide