fix: EvaluationRunResult casting scores from numpy to float

[davidsbatista]

Proposed Changes:

converting scores to str instead of np.float

{'metrics': ['doc_mrr_evaluator', 'faithfulness', 'sas_evaluator'],
 'score': [1.0, np.float64(1.0), np.float64(0.7126952672004699)]}

it looks like this

{'metrics': ['doc_mrr_evaluator', 'faithfulness', 'sas_evaluator'],
 'score': ['1.0', '1.0', '0.7126952672004699']}

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 13923597466

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 6 unchanged lines in 1 file lost coverage.
• Overall coverage remained the same at 90.07%

---

Files with Coverage Reduction	New Missed Lines	%
evaluation/eval_run_result.py	6	61.96%

Totals
Change from base Build 13920793695:	0.0%
Covered Lines:	9724
Relevant Lines:	10796

---

💛 - Coveralls

[sjrl]

@davidsbatista why do we need to cast to string instead of using np.float?

[davidsbatista]

@sjrl see Proposed Changes on the PR notes