fix: correct log placeholder kwarg for untriggered pipeline breakpoint warning

[Kropiunig]

The warning that fires when a pipeline breakpoint is never triggered used the placeholder {break_point} in its message, but passed the value under the kwarg pipeline_breakpoint. Haystack's logger catches the resulting KeyError from msg.format(**safe_extra) and falls back to the raw string, so users saw the literal text {break_point} instead of the actual breakpoint.

Renaming the kwarg to break_point so it matches the placeholder makes the message interpolate the real value. One-line change; the message string is unchanged.

[vercel]

@Kropiunig is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ davidsbatista
❌ Kropiunig
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
haystack-docs	Ignored	Preview	Jul 6, 2026 1:16pm

[davidsbatista]

Hi @Kropiunig - can you please sign the CLA?

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
haystack/core/pipeline
pipeline.py
Project Total

This report was generated by python-coverage-comment-action

[davidsbatista]

Please sign the CLA and then ping me again for review

[github-actions]

Hi @Kropiunig, thanks a lot for your contribution! 🙏

We noticed that the Contributor License Agreement (CLA) check (license/cla) hasn't passed yet, so we've temporarily moved this PR to draft and paused the review assignment.

To get your PR reviewed, please sign the CLA via the link in the license/cla check below (or in the CLA bot comment). As soon as the check turns green, this PR will automatically be marked ready for review again and a reviewer will be re-assigned.

[davidsbatista]

fixed by #12017