feat: add result field for guardrail validation result to support entitlements checks

[apetraru-uipath]

Refactor GuardrailValidationResult to use enum-based result field

Summary

This PR refactors GuardrailValidationResult to align with the new API response format. The model now uses an enum-based result field as the primary indicator of validation status, replacing the boolean validation_passed field.

Changes

Updated GuardrailValidationResultType Enum

• Removed: FAILED, SKIPPED
• Added:
  • VALIDATION_FAILED = "validation_failed"
  • ENTITLEMENTS_MISSING = "entitlements_missing"
  • FEATURE_DISABLED = "feature_disabled"
• Kept: PASSED = "passed"

Simplified GuardrailValidationResult Model

• Removed: validation_passed boolean field
• Updated: result field now has alias="result" and is the primary field
• Kept: reason field for explanatory text

Updated DeterministicGuardrailsService

• Removed all validation_passed parameters from instantiations
• Changed FAILED to VALIDATION_FAILED enum value
• Simplified instantiations to only include result and reason

Test Updates

• Replaced all validation_passed assertions with result enum checks
• Updated 27 tests to use the new format
• All tests pass ✅

Documentation

• Updated comments in _evaluators.py to reflect new result types

Breaking Changes

⚠️ This is a breaking change:

• The validation_passed field has been removed
• Code that directly instantiates GuardrailValidationResult must use the result enum field instead
• Enum values have changed: FAILED → VALIDATION_FAILED, SKIPPED removed

Version

Bumped version from 0.1.4 to 0.1.5