fix(core): change enum consts generation

[Armanio]

closes #2459

• Change enum consts generation
• drop unless eslint commit
• update samples

PS: if anyone can suggest a better title for the enum, I'm ready to listen

[melloware]

Can you rebase this it is conflicted now after the recent PR merges

[anymaniax]

It's a big breaking change no? Also I am not a big fan of just adding Const to it. It's all interest of the enum to have the same name as the type. I have the impression that it's a standard way of doing it like we do it currently. We should maybe find a way to avoid the error for all the linter

[Armanio]

@anymaniax Yes, you're right. This is a breaking change. I was thinking about adding different comments depending on the linter, but I'm not sure that's a good approach. Separating actual values ​​and TypeScript types can be convenient, for example, for searching for values ​​in code.

Anyway, this is a draft; I'm currently running into issues importing types from one file to another.