refactor: FaithfulnessEvaluator specifies inputs explicitly

[julian-risch]

Related Issues

None. Came up in the implementation of ContextRelevanceEvaluator

Proposed Changes:

• FaithfulnessEvaluator specifies run method inputs explicitly
• Move out examples
• Add integration test
• Extend docstring to explain that default examples are used if none are provided

How did you test it?

existing unit tests, new integration test

Notes for the reviewer

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:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 8783754562

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.002%) to 90.065%

---

Totals
Change from base Build 8663731064:	0.002%
Covered Lines:	6255
Relevant Lines:	6945

---

💛 - Coveralls