anbox lxd charm upgrade action output is unhelpful

The output from the anbox lxd upgrade action is messy and confusing, with a lot of out-of-context stdout. And in this example, there is also an error at the end that is misleading (it looks like it's a blocking error, but the return code from the upgrade action was 0 and appeared to work):

$ juju run lxd/0 upgrade
Running operation 93 with 1 task
  - task 94 on unit-lxd-0

Waiting for task 94...
none
Package: anbox-modules-dkms-118
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 53
Maintainer: Indore Team <email address hidden>
Architecture: all
Source: anbox-modules-118
Version: 1:1.18.0-alpha.1+git70e150c~jammy0
Replaces: anbox-modules-dkms
Depends: dkms
Conflicts: anbox-modules-dkms, xtables-addons-dkms
Conffiles:
 /etc/modules-load.d/anbox.conf 79e293ddd4d76ff78f016b3efce53c2b
Description: Anbox Cloud kernel modules in DKMS format
 .
 This package contains a out-of-tree version of the Anbox Cloud
 kernel modules.
Homepage: https://code.launchpad.net/~indore-team/indore/+git/anbox-modules
"lxd" switched to the "+" cohort

fs.inotify.max_queued_events = 1048576
fs.inotify.max_user_instances = 1048576
fs.inotify.max_user_watches = 1048576
vm.max_map_count = 262144
kernel.dmesg_restrict = 1
kernel.pid_max = 65535
net.ipv4.neigh.default.gc_thresh3 = 8192
net.ipv6.neigh.default.gc_thresh3 = 8192
kernel.keys.maxkeys = 2000
kernel.keys.maxbytes = 2000000
fs.aio-max-nr = 524288
sysctl: setting key "net.ipv4.ping_group_range": Invalid argument
```

It would be good to have the output a bit cleaner with more useful information, such as current lxd version, the version it has upgraded to, success/failure message at the end, etc.