Fix #9620 better error handling of GeoProcessing

[MV88]

Description

Error described in the issue now provides a feedback and the app does not crash with specific use case

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Issue

What is the current behavior?

Fix #9620
Fix #9603

What is the new behavior?

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[offtherailz]

For sure this exception is not handled.
We have a lot of layers and use cases where things do not work. Use them to test.
screencast-bpconcjcammlapcogcnnelfmaeghhagj-2023.10.18-13_06_22.webm

I'm going to review this better when you think that all the exceptions are correctly handled

[offtherailz]

It improved a lot. It works well for me.
Please change the text about the source layer, because a source layer as line is anyway accepted.

Question:
I tried an intersection between raoads and streams, I have no results (theoretically I should have some points)
I tried an intersection between roads and roads, it worked.

I think this is a bug/missing feature of the process.

[ElenaGallo]

Test passed @MV88 please backport to the stable branch. Thanks

[MV88]

backport here #9630