refactor: AnswerExactMatchEvaluator component inputs

[masci]

Related Issues

• fixes feat: AnswerExactMatchEvaluator input should be one answer per query instead of list of answers #7459

Proposed Changes:

Change the component inputs as described in the attached issue

How did you test it?

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 8658195269

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.
• 33 unchanged lines in 6 files lost coverage.
• Overall coverage increased (+0.1%) to 90.063%

---

Files with Coverage Reduction	New Missed Lines	%
core/serialization.py	2	95.83%
core/pipeline/descriptions.py	3	54.55%
core/component/sockets.py	4	85.71%
telemetry/_environment.py	6	84.21%
logging.py	7	93.16%
core/pipeline/pipeline.py	11	94.05%

Totals
Change from base Build 8648609512:	0.1%
Covered Lines:	6254
Relevant Lines:	6944

---

💛 - Coveralls

[julian-risch]

Looks good to me! 👍 I just updated the docstring. It still referred to the old logic.
The release note looks great! We didn't include evaluation features in any earlier release. That's why I don't see a need to include the upgrade steps in the release notes of Haystack 2.1.0. In this particular case, it would be better to update this note instead: https://github.com/deepset-ai/haystack/blob/main/releasenotes/notes/exact-match-evaluator-197bb87b65e19d0c.yaml

[julian-risch]

@dfokina The draft of the documentation page is already up to date with the changes made in this PR.