stack/monitor: point monitor_genstatus to monitor.genstate binary

Summary

stack/slapos.cfg was bumped to slapos.toolbox = 0.165 (in commit c74787db9 on master), which renamed the entry point from monitor.genstatus to monitor.genstate. stack/monitor/buildout.cfg still references the old binary path, so any partition using the monitor stack on a fresh deploy fails:

ionice: failed to execute .../bin/monitor.genstatus: No such file or directory
monitor-globalstate-first-run: Non zero exit code (127) while running command.

This breaks initial deployment of any SR depending on the monitor stack with the current toolbox pin (e.g. rapid-cdn, where it manifests as a kedifa-login-csr precondition failure on frontend partitions because kedifa never finishes deploying).

Change

One line in stack/monitor/buildout.cfg:77 — point the monitor_genstatus jinja context variable to the new monitor.genstate binary path. Variable name kept as-is to minimize the diff (no consumer needs to change).

Note

A more thorough rename (with section names + an unrelated logrotate addition) exists as 06d37355e on the monitor-history branch, but it bundles a slapos.toolbox version downgrade (0.162→0.164) that conflicts with current master's 0.165 and references unrelated changes from slapos.package MR 226. This MR is the minimal targeted fix.

Test plan

• Locally reproduced the failure on a fresh build (rapid-cdn TestMasterRequest fails with the kedifa-login-csr precondition + exit-127 error in node-instance log).
• After applying this 1-line fix, locally Ran 7 tests in 259.310s. OK.