fix(types): tools export types added

[neSpecc]

Problem

Some compilers can't build projects with current editor.js import because of errors like that

node_modules/.pnpm/@[email protected]/node_modules/@editorjs/editorjs/types/api/tools.d.ts:1:22:
  1 │ import BlockTool from "../../src/components/tools/block";

Resolves #2771

Cause

In #2718 we introduced api.tool.getBlockTools() method that returns BlockTool[] objects which declared under the npmignored /src folder.

Solution

Confusing names

We have a confusing names in src/components/tools/:

• BlockTool — it is not a block tool (see types/tools/block-tool.d.ts). It is more like block tool adapater
• same with InlineTool and BlockTune

So I've renamed them to BlockToolAdapter, InlineToolAdapter, BlockTuneAdapter across all the code.

Now BlockTool has only one meaning declared in types/tools/block-tool.d.ts

Types for adapters

I've manually created types for adapters:

/types/tools/adapters/block-tool-adapter.d.ts
/types/tools/adapters/inline-tool-adapter.d.ts
/types/tools/adapters/block-tune-adapter.d.ts

Classes in src/components/tools/ implements those adapters interfaces.

Also

• Enums are moved to /types as well, but under .ts files instead of d.ts (complier can't find enums values in d.ts)
• Popover types are moved to /types as well
• Added @/types alias
• Eslint now enforces to use "import type" when only type is needed.

We manually maintain /types which may be not-best solution today. We can consider autogenerating types in a future.

[golodnoy]

HI @neSpecc
There are still bugs in the new version of the library. Please fix them