Fix ghostel-debug advice arity for redraw-now's FORCE argument

[dakra]

Problem

#460 gave ghostel--redraw-now an optional FORCE argument ((buffer) → (buffer &optional force)). Adding an &optional arg is safe for plain callers, but advices capture arity — and the ghostel-debug advices that wrap ghostel--redraw-now still declared the old single-argument form. When debug logging or latency profiling is active, the forced redraw paths (ghostel-force-redraw, the reappear hook ghostel--window-buffer-change) signal wrong-number-of-arguments:

• ghostel-debug--log-redraw (:around) received three args into a two-parameter lambda, and dropped FORCE when forwarding to the original.
• ghostel-debug--latency-on-render (:after) received two args into a one-parameter lambda.

This was reported in #456 (review of #460).

Beyond the regression, ghostel-debug--log-resize (:around on ghostel--adjust-size) had the same latent bug already: ghostel--adjust-size has taken an optional FORCE for a while (a text-scale change passes it), so the resize advice would crash there too.

Notably, this also blocks diagnosing the other open parts of #456: ghostel-debug-start installs these advices, so switching workspaces (→ forced reappear redraw) throws before any useful log is produced. This fix is a precondition for debugging the rest.

Changes

• ghostel-debug--log-redraw: accept &optional force, forward it, and fold it into the skip prediction and the force=… log column so the log stays truthful for arg-forced redraws.
• ghostel-debug--latency-on-render: accept &rest _ (ignores the arg).
• ghostel-debug--log-resize: accept and forward &optional force (the pre-existing latent bug).
• test/ghostel-ime-test.el: refresh the stale declare-function arity.
• test/ghostel-debug-test.el: regression test asserting both redraw-now advices tolerate and forward FORCE.

Only affects sessions with ghostel-debug-start / latency profiling active; normal sessions were unaffected.

make -j8 all is green.