Rename dialects to custom preprocessors and add "real" dialect support.

[ishche]

Based on #1891 (comment)

@VitGottwald @ap891843 @Nurkambay @zimlu02

1. Should we rename dialects into preprocessors in the project?
2. Do you think the impact on customers will be significant?
3. Should we plan support for COBOL dialects in the future?

[VitGottwald]

1. Where do you think we would need to do the rename and what would be the effort? In processor groups we already call it preprocessor and in the marketplace extension names we have not used the term dialect at all (e.g. "COBOL Language Support for IDMS")

[VitGottwald]

@ishche ^^^

[ishche]

I think we have it in the settings

che-che4z-lsp-for-cobol/clients/cobol-lsp-vscode-extension/package.json

Line 390 in 729a308

"cobol-lsp.dialects": {

,
in the class names, and there are plenty of IDs to rename.

[GitMensch]

The sample from package.json is moved two lines down with the current version; the main question is when this is done (hopefully before any more dialect/preprocessor work).

In any case this possibly should get the custom-dialect label.