fix: only add activity output property if not none

[LeonardHd]

This PR fixes an issue where activity properties with None values were incorrectly included in the activity result dictionary, causing that no parameter not found errors are thrown when expressions tried to access non-existent properties as they are passed as None.

• Updates the expression evaluator to only include activity properties in the output body when they are not None
• Changes the default status from being automatically set to SUCCEEDED to allowing explicit None values
• Adds comprehensive test coverage for scenarios where activity properties are None

Fixes #164

[Copilot]

Pull Request Overview

This PR fixes an issue where activity properties with None values were incorrectly included in the activity result dictionary, causing parameter not found errors when expressions tried to access non-existent properties.

• Updates the expression evaluator to only include activity properties in the output body when they are not None
• Changes the default status from being automatically set to SUCCEEDED to allowing explicit None values
• Adds comprehensive test coverage for scenarios where activity properties are None

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/data_factory_testing_framework/state/_activity_result.py	Removes automatic defaulting of status to SUCCEEDED, allowing explicit None values
src/data_factory_testing_framework/_pythonnet/data_factory_testing_framework_expressions_evaluator.py	Implements conditional inclusion of activity properties, only adding them to output body when not None
tests/unit/functions/test_data_factory_testing_framework_expression_evaluator.py	Adds parameterized test to verify proper error handling when accessing None activity properties