feat: add support for skipping scenarios via SkipScenarioException

[serhatozdursun]

Overview

This PR addresses issue #691 by introducing native support for skipping scenarios

🔧 Changes Made

• ✅ Introduced SkipScenarioException, which can be thrown to trigger a skip.
• ✅ Updated MethodExecutor to catch SkipScenarioException, mark the step as skipScenario = true, and prevent it from failing.
• ✅ Included SKIPPED: <reason> messages in the execution result.
• ✅ Extended StepExecutionStageTest with a new test: testStepMethodExecutionWithSkipScenarioException.

[chadlwilson]

Did you resolve your challenge/confusion noted in the discussion at #691 (comment) ?

[serhatozdursun]

@chadlwilson I realized that my initial approach was incorrect, so I rolled back those changes. I’ve now aligned the solution with the approach used in gauge-python/pull/397 which addresses the issue described in gauge-python/issues/390

[serhatozdursun]

@chadlwilson
I added the following lines to ensure the skipScenario flag is preserved across execution stages:

boolean skipped = execResult.getSkipScenario() | previousStageResult.getSkipScenario();
builder.setSkipScenario(skipped);

Without this, a skipped scenario would be incorrectly treated as passed when results are merged.
This change ensures that the skipped state is maintained correctly and reflected in the final execution report.

[chadlwilson]

Cool - seems to make sense. I am not familiar with the merge logic but when you've addressed the checkstyle errors and signed your commits I'll take a deeper look :-) https://github.com/getgauge/gauge-java/pull/924/checks?check_run_id=42041532879

[gaugebot]

@serhatozdursun Thank you for contributing to gauge-java. Your pull request has been labeled as a release candidate 🎉🎉.

Merging this PR will trigger a release.

Please bump up the version as part of this PR.

Instructions to bump the version can found at CONTRIBUTING.md

If the CONTRIBUTING.md file does not exist or does not include instructions about bumping up the version, please looks previous commits in git history to see what changes need to be done.

[chadlwilson]

Thx - the stage merging is still a bit confusing to me, but seems to me it might have the problem you mention if the skip scenario exception is thrown during a hook rather than during the step itself, or thrown during the step and for a method which has an "after" hook that applies. But I'm also not super familiar with the hooks.

Anyway, I've added a test for that exec result merging, tidied up a bit and will release this. I also changed the message to emit directly what people put in their exception message to return full control to the user rather than prefixing with SKIPPED: (similar to the other language plugins).