fix: let updates finish when plugins change no config and openclaw.json is read-only (#201331)

* fix(update): publish plugin records without an empty config write

When plugin convergence after a core update changes no config path, publish the install records without writing openclaw.json. A config file the update cannot replace, such as a link to a provisioned read-only file, no longer fails an update whose plugin work converged, and the file keeps its bytes. A real config change against such a file is still refused.

The update report for a healthy Gateway with unfinished maintenance now names `openclaw gateway stop --force`, the command that works in a non-interactive shell and the one repair names.

Adds the published-driver-plugin-publication Docker lane: a published 2026.11.5 updater's first update with two official npm plugins and a symlinked read-only config.

* test(e2e): record the published-driver plugin cell before asserting

* test(update): keep the post-Doctor publication check on a real config change

* fix(update): bind records-only plugin publication to the planned config path

Check the config path proof captured for the update before and after the records-only publication, so a re-pointed config link cannot receive records planned for another config. The published-driver cell now pins its baseline plugin versions through a fixture registry and requires readable update history that names the update's own run.

* test(e2e): isolate and bound the published-driver plugin publication cell

Give the lane its own artifact directory, read readiness only from a successful probe in this run, bound fixture fetches by the cell deadline, and add a refused-channel-change mode: a real config write against the read-only config still fails the update, and the report names a Gateway stop that works unattended.

* test(e2e): pin the refused channel write and the cell's own artifact default

The negative control now requires the symlink refusal in post-update verification, the wrapper selects the plugin publication cell's artifact directory with its entry point, and the plugin observation is named after the local inventory it reads.

* test(e2e): default the plugin publication cell to a release and pin the refused control's plugins

* test(e2e): stamp lane plugin fixtures with the core target and check the config link itself