updateProcess: fix incorrect arguments, swap them back in correct order

[mpl]

updateProcess was called with the correct arguments only in the "run once" case, but not in the periodic run case.

[damdo]

Yes! I have fixed this issue locally in the PR I'm working on, it still hasn't made its way here though. Thank you for fixing it!

[damdo]

cc. @stapelberg for the merge

[mpl]

hah. I was wondering if you all were just using selfupdate in the run once case. :)

Since we're here, I'd like to run something by you:
I find it a bit inconvenient that there is no mode where you are in the periodic case, but where there is also an immediate run nonetheless.
So I was thinking the code could become something like:

	log.Print("skipping waiting, performing an immediate updateProcess")
	if err := updateProcess(ctx, gusCli, machineID, o.gusServer, sbomHash, o.destinationDir, httpPassword, httpPort); err != nil {
		// If the updateProcess fails we exit with an error
		// so that gokrazy supervisor will restart the process.
		return fmt.Errorf("error performing updateProcess: %v", err)
	}

	if o.skipWaiting {
		// If the updateProcess doesn't error
		// we happily return to terminate the process.
		return nil
	}

Would you be against something like that? (Do you want me to open an issue about it to discuss it?)

[damdo]

hah. I was wondering if you all were just using selfupdate in the run once case. :)

I was using it in the run once yes, so I only caught this last weekend, when I changed modes in development.

Let's open a separate conversation for the other one :)
I'll create an issue now.

[damdo]

Created #6 for that @mpl @stapelberg