Set the chamber light on in printer.base.cfg too

a70462b lit the chamber by overriding initial_WHITE from ff-chamber.cfg,
deliberately leaving printer.base.cfg as FlashForge shipped it. This puts
the same option in the base file as well, which is what was actually
wanted.

Both are now set. They do not fight: Klipper parses with
RawConfigParser(strict=False), so the two [led chamber_led] sections
merge and the later file simply restates the same 1.0.

The cost is a standing warning. bin/unpack.sh:61 diffs our
printer.base.cfg against the stock one from whichever package the build
is pointed at, comparing section and option lines with only comments,
blanks and the chamber-heater block filtered out. initial_WHITE is a
real option line, so from now on every unpack prints

    !! printer.base.cfg DIFFERS from this package's stock file.

That check exists to notice FlashForge changing a pin map, a stepper
current or an endstop under us. It is a warning and not a gate -- the
build still succeeds -- but it will now fire on every run, which is how
a useful warning stops being read. If that becomes a nuisance, the fix
is to add initial_WHITE to the strip filter in unpack.sh rather than to
drop the line here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

payload/klipper/config/printer.base.cfg

@@ -136,6 +136,7 @@ stall_threshold: 0.6
 [led chamber_led]                                                   
 white_pin: PB5                                                
 hardware_pwm: False 
+initial_WHITE: 1.0
 
 [heater_fan heat_fan]
 pin:eheaterboard:PC11