Centralized unit update management

[Tbaile]

From the Controller it should be possible to update the Unit seamlessly (packages and/or image).

This is due the feature added in the controller that avoids UI - API version mismatch and inherently avoids accidental misconfigurations.

Here's the list of the actions that are to be implemented in the controller:

• Unit Actions Section

  • Add the action to schedule an update
  • Add the action to abort an update
  • Add the action to reschedule an update
  • Optional Add the action to force pull and install the packages

• Bulk Actions Section

  • Add the action to update Unit Image (scheduled or now)

• Add next to the version a warning sign indicating that there's an image update available for the unit alternatively a clock indicating that there's a scheduled update planned for the unit

---

PRs:

• feat(api): added additional fields coming from unit nethsecurity-controller#45
• ns-api(controller): added additional information for the controller #801 (not needed)
• chore: version update ns8-nethsecurity-controller#43
• feat(controller): add remote unit update nethsecurity-ui#370

[Tbaile]

While it's not completed and merged, the changes are only needed to be made to the controller.
Testing is enabled doing so:

1. On a NS8 machine, install and configure the controller with

add-module ghcr.io/nethserver/nethsecurity-controller:unit-remote-update

2. Prepare 3 units that are 1.0.1, 1.1.0 and 1.2.0.
3. Connect all units to the controller, manually refresh the info for each unit, then the following must apply:
   3.1: Unit 1.0.1 and 1.1.0 must show a Update available
   3.2: Unit 1.2.0 mustn't show any labels.

QA:

1. Check if scheduling an update works, this can be done on both 1.0.1 and 1.1.0
2. Try to cancel a scheduled upgrade
3. For one unit, launch a image update directly and wait for it to boot up, try to access the unit (careful, openWRT sessions are long, unit might still appear connected while not so.). In addition the unit won't be having any info fetched because it's a cron, a "Update available" might still be there.
4. Check if fetching package update works. (on 1.2.0 due to a restart of ns-api-server this might trigger a issue, ONCE)
5. Try the "Update units" batch command.

[gsanchietti]

The feature works well, but the controller's UI is not very clear and does not provide immediate feedback, which could confuse the user and generate support requests.

These are the current issues:

• when I start the immediate update of the unit, the update takes a few seconds to start (in my case at least a minute because I have a slow connection for the download); I have no feedback in the UI and cannot understand which unit I tried to update if I have many that require updating
• after the update, a unit remains marked as "to be updated" until the data is refreshed (which can take up to 30 minutes), or until I try to update it again, in which case the status is updated immediately and the "to be updated" label disappears.
• I schedule an update from the controller, the "scheduled update" label appears; I go to the unit and remove the scheduled update; the change is not reflected on the controller until the information is refreshed (30 minutes).
• I schedule an update from the controller, the "scheduled update" label appears; the unit performs the update; the "scheduled update" label remains until the unit communicates the data (30 minutes).

[Tbaile]

NSEC Version: 23.05.5-ns.1.2.99-alpha1-74-g49bad6b4eb
Controller: ghcr.io/nethserver/nethsecurity-controller:main

[gsanchietti]

All previous issues are now addressed with latest image.
Please note that when using the controller with old images, some glitches may still appear.