fix: include because-reason when verifying that an exception is thrown

[vbreuss]

When an "And" node (or an "Or" node) has an empty node, this node is ignored during evaluation, but the because reason is applied to it.
In this case, the because reason should instead be applied to the latest previous node.

• Fixes Because not included when checking for a delegate to throw #654

[Copilot]

Pull Request Overview

This PR ensures that exception verification tests include a clear "because" reason, refines the logic for setting the reason in expectation nodes, and adjusts the build pipeline configuration to target core-only builds.

• Updates exception verification tests to include an explanatory reason.
• Refactors the SetReason logic in OrNode and AndNode to handle empty expectation nodes.
• Changes the BuildScope in the build pipeline from Default to CoreOnly.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
Tests/aweXpect.Tests/Delegates/ThatDelegate.ThrowsException.Tests.cs	Enhances exception verification tests with a "because" reason to improve clarity.
Source/aweXpect.Core/Core/Nodes/OrNode.cs	Adapts SetReason to delegate to a child node if the current expectation node is empty.
Source/aweXpect.Core/Core/Nodes/AndNode.cs	Adapts SetReason to delegate to a child node if the current expectation node is empty.
Pipeline/Build.cs	Updates BuildScope configuration to build only core components.

Comments suppressed due to low confidence (1)

Pipeline/Build.cs:22

• Update the accompanying documentation or comments to clarify the reasoning behind changing the BuildScope from Default to CoreOnly.

	readonly BuildScope BuildScope = BuildScope.CoreOnly;

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

Measures
0 Security Hotspots
60.0% Coverage on New Code
100.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

This is addressed in release v2.18.0.