fix: Allow string values for FlagEvaluationDetails.reason and FlagResolutionDetails.reason

[keelerm84]

This PR

Expands the types allowed for reason on FlagEvaluationDetails and FlagResolutionDetails to include both Reason and str types.

Related Issues

Fixes #262

Notes

Related to spec issue: open-feature/spec#236

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f1b0839) 93.89% compared to head (fd30717) 93.89%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #264   +/-   ##
=======================================
  Coverage   93.89%   93.89%           
=======================================
  Files          16       16           
  Lines         442      442           
=======================================
  Hits          415      415           
  Misses         27       27           

Flag	Coverage Δ
unittests	93.89% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[gruebel]

Nice job 🍻

[lukas-reining]

Not a huge python expert but the change and tests look good!

[federicobond]

Hi @keelerm84! Thank you for your contribution. Change LGTM, but I am lost on what the test is supposed to assert.

If it's just a type check then it should be already covered by mypy. Would any of the tests break if you reverted the type change?

[keelerm84]

Hi @keelerm84! Thank you for your contribution. Change LGTM, but I am lost on what the test is supposed to assert.

If it's just a type check then it should be already covered by mypy. Would any of the tests break if you reverted the type change?

That's a good point. I've removed the useless test and will rely on mypy as suggested.