feat: Add evaluation details to finally hook stage

[askpt]

Add evaluation details to the finally hook stage

This pull request includes several changes to improve the handling of flag evaluation details and error handling in the OpenFeature library. The most important changes include modifying hook methods to accept FlagEvaluationDetails as a parameter, updating the EvaluateFlagAsync method to handle provider errors more gracefully, and adjusting the corresponding unit tests to reflect these changes.

Related Issues

Fixes #328

Notes

Improvements to Hook Methods:

• src/OpenFeature/Hook.cs: Modified the FinallyAsync methods to accept FlagEvaluationDetails as a parameter. [1]
• src/OpenFeature/Hook.cs: Modified the hooks methods to split the parameters per line.[1] [2] [3]

Enhancements to Flag Evaluation:

• src/OpenFeature/OpenFeatureClient.cs: Updated the EvaluateFlagAsync method to initialize FlagEvaluationDetails in case of provider errors and ensure the FinallyAsync hook is always called with the correct evaluation details. [1] [2] [3]

[codecov]

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 85.13%. Comparing base (2774b0d) to head (c88e301).

Files with missing lines	Patch %	Lines
src/OpenFeature/OpenFeatureClient.cs	80.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #335      +/-   ##
==========================================
- Coverage   85.17%   85.13%   -0.04%     
==========================================
  Files          36       36              
  Lines        1477     1480       +3     
  Branches      150      151       +1     
==========================================
+ Hits         1258     1260       +2     
  Misses        188      188              
- Partials       31       32       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[beeme1mr]

Could you please add a test to ensure that the evaluation details included in the final stage match what's returned to the user? Here's how requirement 4.3.8 was tested in JS.

https://github.com/open-feature/js-sdk/pull/1087/files#diff-5eb44a4c1dd2a0d07e4b54e1eab5d69c60cc983aad849aeae08567fb85af2b3f

Thank!

[askpt]

Could you please add a test to ensure that the evaluation details included in the final stage match what's returned to the user? Here's how requirement 4.3.8 was tested in JS.

https://github.com/open-feature/js-sdk/pull/1087/files#diff-5eb44a4c1dd2a0d07e4b54e1eab5d69c60cc983aad849aeae08567fb85af2b3f

Thank!

@beeme1mr I added the specification test with: 25af4ba

I hope it is what you were expecting.

[toddbaert]

Will merge/release this next week unless I hear objections. We'll have to do some manual release notes as well when we do, as we did with JS: https://github.com/open-feature/js-sdk/releases/tag/web-sdk-v1.4.0

See also, same change in Java: open-feature/java-sdk#1262