printnanny-cloud-nats.service + printnanny-cloud-sync.service should be disabled on first boot, then enabled after cloud account connected

[leigh-johnson]

Describe the bug

The following systemd services are enabled (automatically start at boot) in PrintNanny OS v0.4.x image, which leads to the first boot always reporting as "degraded"

printnanny-cloud-nats.service
printnanny-cloud-sync.service

Switch these services to disabled in the next image release, then enable them only after a PrintNanny Cloud account is connected.

To Reproduce

What are the steps to reproduce the issue?

1. Burn a v0.4.1 image
2. Let first boot finish
3. Notice: systemd reports degraded state because printnanny-cloud-nats and printnanny-cloud-sync are in a failed state.

Expected behavior

1. Burn a PrintNanny OS release image
2. Let first boot finish
3. First boot should report success
4. Connect PrintNanny Cloud account via PrintNanny OS dashboard
5. cloud nats/sync services should now be enabled
6. Reboot - cloud nats/sync enabled state should persist and boot status should still report success

Issue.txt

-----------------------
Build Info:  |
-----------------------
IMAGE_NAME = printnanny-release-image-raspberrypi4-64-20221101163620
DISTRO_PRETTY = PrintNanny Linux 0.4.1 (Dunite)
VARIANT_NAME = PrintNanny OS Core
VARIANT_ID = core
DISTRO = printnanny
DISTRO_NAME = PrintNanny Linux
DISTRO_VERSION = 0.4.1
DISTRO_CODENAME = Dunite
ID_LIKE = BitsyLinux
HOME_URL = https://printnanny.ai
BUG_REPORT_URL = https://github.com/bitsy-ai/printnanny-os/issues
YOCTO_VERSION = 4.0.2
YOCTO_CODENAME = Langdale
MACHINE = raspberrypi4-64
TUNE_PKGARCH = cortexa72
-----------------------
Layer Revisions:      |
-----------------------
meta              = langdale:6b9db5a99bf0fab47219d4648f4663c4397ac87f
meta-poky         = langdale:6b9db5a99bf0fab47219d4648f4663c4397ac87f
meta-yocto-bsp    = langdale:6b9db5a99bf0fab47219d4648f4663c4397ac87f
meta-raspberrypi  = master:722c51647c75d63e8c6c53ee214c4e3f0a263ed2
meta-oe           = langdale:c5668905a6d8a78fb72c2cbf8b20e91e686ceb86
meta-python       = langdale:c5668905a6d8a78fb72c2cbf8b20e91e686ceb86
meta-multimedia   = langdale:c5668905a6d8a78fb72c2cbf8b20e91e686ceb86
meta-bitsy        = openssl-3-0-7:6caadd5ffe32c7f9f7c74f22cfb590b08ad24da8
meta-neural-network = master:1d70eb6c0f6d5a7d5dc904ae988a7e152b52267e -- modified
meta-printnanny   = openssl-3-0-7:6caadd5ffe32c7f9f7c74f22cfb590b08ad24da8
meta-networking   = langdale:c5668905a6d8a78fb72c2cbf8b20e91e686ceb86
meta-filesystems  = langdale:c5668905a6d8a78fb72c2cbf8b20e91e686ceb86
meta-initramfs    = langdale:c5668905a6d8a78fb72c2cbf8b20e91e686ceb86
meta-webserver    = langdale:c5668905a6d8a78fb72c2cbf8b20e91e686ceb86
meta-swupdate     = master:5e611f44db1b9333342ed61d77a3c3ed7be69c2b
workspace         = langdale:6b9db5a99bf0fab47219d4648f4663c4397ac87f
meta-microcontroller = master:9f396e595b2d639be7f2b494f4a61e48d9495058

ℹ️ You can find /boot/issue.txt on your SD card. You can also find the contents of issue.txt in OctoPrint's Settings > OctoPrint-Nanny > Report Issue tab.

[leigh-johnson]

🎉 Done! Changes will be in v0.4.2, releasing tomorrow.