0.2.41 - cloud 403 fixed on audit-blocked OrcaSlicer builds

Fixed cloud print failing with HTTP 403 and an empty camera feed on OrcaSlicer builds that block the plugin from its own config file (reported from an A1 on Windows 11, OrcaSlicer 2.5.0-alpha).

When OrcaSlicer's plugin audit denies the installer all access to obn.conf, the client_name rewrite and the log_to_file default were skipped, so a stale client_name = OpenBambooNetworking made the cloud answer 403 on print registration and on the camera mint, with no obn.log to diagnose it.

The installer now applies block_cloud, log_to_file and client_name through the library in a single call that runs outside the audit hook: prints work without hand-editing obn.conf, and obn.log exists for the next report. A config created fresh at install time also gets log_to_file = 1. Explicit user values are never touched, and older libraries keep the previous behavior.

Libraries rebuilt from open-bamboo-networking 85c2b52 on all three platforms.