[UX] Export/Import categories data

[arielj]

This PR adds the actions to export the categories to a JSON file and also the option to import a JSON file with categories information.

For now it exports the categories inside the Games/Heroic folder, so we can be sure Heroic flatpak will have write access to it.

The buttons are at the bottom of the Manage Categories modal:

Closes #3416

---

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[flavioislima]

LGTM

[CommandMC]

I don't think having the buttons in the modal itself makes sense, since they offer functionality you don't need often. Tucking them somewhere into the settings, or at least making the buttons less prominent, would be ideal

[arielj]

I don't think having the buttons in the modal itself makes sense, since they offer functionality you don't need often. Tucking them somewhere into the settings, or at least making the buttons less prominent, would be ideal

maybe I can hide the 2 buttons inside a <details> tag collapsed by default?

what I like about the buttons in the modal is that it makes it really easy to discover them, it's right next to where categories are managed

I think collapsing them and show them only on demand can help clean it up and keep them easily discoverable, I'll update the PR

[arielj]

This is how it looks like now, collapsed by default

[CommandMC]

Sorry for another nitpick, testing things now:

• One button says "Export to file", the other "Import file". To keep them consistent, I'd either change the one to "Export file", or the other to "Import from file"
• Maybe add icons to the buttons?

[CommandMC]

This feels like an obvious use case for Zod

// Somewhere at the start of the file
const ImportSchema = z.record(z.string(), z.string().array())

// Inside the function
const jsonContent = JSON.parse(content)
const validatedContent = ImportSchema.parse(jsonContent)
// validatedContent is now of type Record<string, string[]>

If we truly want to accept partially-malformed category exports, we could still handle that in Zod with some transforms. IMO we should just not do that though, I don't think that's a common use case

[CommandMC]

Since you seem to be looking to create more exporters/importers, you may want to create a "category" for those IPC functions. It makes them easier to find & lessens the load on the language server (well, it would if we had more of them)

A "category" is just an object with properties, like this example:

HeroicGamesLauncher/src/preload/api/settings.ts

Lines 20 to 23 in 23de3f9

	export const systemInfo = {
	get: makeHandlerInvoker('getSystemInfo'),
	copyToClipboard: makeListenerCaller('copySystemInfoToClipboard')
	}

(whether you sort them export.categories or categories.export is up to you)

[arielj]

yes, the idea is that we could have more importers/exporters for other things in the future, like the app settings for example that users currently have to copy around internal files