[updater] Config fields required even if set at runtime

[bicarlsen]

For updater it is possible to set all the required config fields at runtime: endpoints, public key. However, it is still required that the { "plugins": { "updater": { "pubkey" } } } field exists in the conf file.

You can get around this by setting the field to any value (e.g. { "plugins": { "updater": { "pubkey": "<SET AT RUNTIME>" } } }), but it seems this should be unnecessary.

[bicarlsen]

It also seems to be the case that the update server is not pinged if there are no endpoints specified in the conf file, even if there are some set at runtime.

[MGough]

I encountered an issue that I think is related. I hadn't set { "plugins": { "updater": {...}}} at all in my tauri.conf when migrating from v1 to v2, as previously we had separate configs that were merged in during our CI build for updates, but not for local builds.

This resulted in the built app immediately crashing on launch on MacOS without any errors anywhere, while the development version worked fine.

The plugin should probably be resilient to these fields being missing as above, and to log warnings if they are missing.