refactor: Implementation for the new mapping

[Nurkambay]

This refactoring will fix the following issue: #1854

1. Pay attention to the org.eclipse.lsp.cobol.common.mapping package.
   It contains a new implementation for the mapping. Other changes are just changes due to interface changes.

2. Also there are some changes with tests. Some tests were updated due to better mapping and a few tests were disabled because of limitations in the use cases test suit. server/engine/src/test/java/org/eclipse/lsp/cobol/usecases

[VitGottwald]

I download the artefacts (vsix-cobol-language-support-darwin-x64.zip, vsix-idms-dialect.zip, vsix-daco-dialect.zip) and tested on internal repo. It fails on every DaCo program. Will DM you on slack.

[VitGottwald]

Since these changes affect the core functionality and some tests were disabled, please run the internal test suite and do a manual smoke test on the internal repo before proceeding.

[Nurkambay]

Since these changes affect the core functionality and some tests were disabled, please run the internal test suite and do a manual smoke test on the internal repo before proceeding.

Thanks, I have added a use case test for it. Should be covered by unit tests now

[VitGottwald]

Now both IDMS and DaCo code gets properly analysed. But now I am getting a random dance of errors showing up and disappearing when enter code. Maybe worth running the typing test?

[Nurkambay]

Looks like it is something broken in the processing itself, i will check it in dev

[Nurkambay]

Now both IDMS and DaCo code gets properly analysed. But now I am getting a random dance of errors showing up and disappearing when enter code. Maybe worth running the typing test?

I have checked it. It is completely the same functionality as we have on development. Looks like when we have errors we have faster processing then expected and that's why we can see these errors. And we have the same in the development branch.

[ap891843]

👍