[Feature Request] Use typescript enum for IPC routes

[Freymaurer]

I used IPC routes in the Swate view, which were renamed some time ago, without adapting the calls in the SwateView.

ARCitect/packages/renderer/src/views/SwateView.vue

Lines 90 to 104 in 57fa8e2

	RequestPaths: async (selectDirectories: boolean) => {
	let selection = null;
	let options: Electron.OpenDialogOptions = {}
	options.defaultPath = ArcControlService.props.arc_root!;
	if (selectDirectories) {
	selection = await window.ipc.invoke("LocalFileSystemService.selectAnyFolders")
	} else {
	selection = await window.ipc.invoke("LocalFileSystemService.selectAnyFiles")
	}
	if (selection === null || selection.length < 1) return;
	if (selection[0].startsWith(ArcControlService.props.arc_root)) {
	selection = selection.map((p: string) => p.replaceAll(ArcControlService.props.arc_root!, "."))
	}
	send(Msg.PathsToSwate, selection)
	},

cdeec89#diff-06a1adc8d17d7cee6fb88a8d3554ec88abb50f54b3350dbfc35c2b84eb1ab1c5L231-L234

This lead to issues for our users: nfdi4plants/Swate#518

I propose we use a typescript enum for all future ipc calls. This would give us more security in finding such errors.

Example:

[JonasLukasczyk]

If we keep both the string and enums then this just results in code bloat, i.e., a lot of redundancy . We could switch to a pure enum based IPC interface but I would give this a low priority.

[Freymaurer]

The images above serve only as an example. All IPC routes should be replaced by this setup