Include file path in patch apply exception messages

[jkschneider]

Summary

• Updated PatchApplyException messages to include the file path being patched
• Now uses the existing patchApplyErrorWithHunk message template instead of patchApplyException
• Provides better context for debugging patch application failures

Problem

When a patch fails to apply, the error message only included the HunkHeader (line start/count info), but not which file was being patched. This made debugging difficult since the same hunk pattern could occur in multiple files within a patch.

Before:

Cannot apply: HunkHeader[1,5->2,6]

After:

Error applying patch in src/main/java/Foo.java, hunk HunkHeader[1,5->2,6]: hunk does not apply to file content

Solution

Changed four exception throws in ApplyCommand.applyText() to use the patchApplyErrorWithHunk message template which accepts the file path as its first parameter:

1. Hunk out of sequence - When hunks are not properly ordered
2. Cannot apply hunk - When a hunk with newStartLine=0 can't be applied
3. Hunk position overlaps - When hunk application position conflicts with previous hunk
4. Hunk does not apply - When hunk content doesn't match file content

Test plan

• Code compiles successfully

• Existing message templates already existed but were unused

• Fixes moderneinc/customer-requests#1759