fix(tui): log debug file errors

[resolvicomai]

What?

• Route debug image protocol log writes through a helper that checks write and close errors.
• Log failures for DEBUG_IMAGE_PROTOCOL_LOG and DEBUG_KITTY_LOG instead of silently ignoring them.
• Add regression coverage for write and close failure paths.

Closes #698
Closes #699

Why?

The Kitty/image protocol debugger previously ignored both WriteString and Close errors when writing debug logs, which could hide failed diagnostics and resource cleanup problems.

Tests

• go test ./view -count=1 -run TestDebugImageProtocolReportsLog
• go test ./view -count=1
• go test ./...
• make lint

[floatpanebot]

Hi @resolvicomai! Please fix the following issues with your PR:

• Body: Missing the ## What? or ## Why? headings required by the PR template.

Formatting issues have been resolved. Thank you!

[FromSi]

lgtm

[andrinoff]

@resolvicomai we are migrating to a new log introduced in #1311. Please use loglevels internal package

[resolvicomai]

Thanks. I pushed a follow-up that routes both debug-log paths through the internal loglevel package:

• image protocol debug output and file-error logging in view/html.go
• kitty body-selection output and file-error logging in fetcher/fetcher.go

Validation:

• go test ./view ./fetcher
• go test ./...
• make lint
• git diff --check

[andrinoff]

conflicts @resolvicomai