Align save collection call with overall project architecture

[n14s]

The common approach for api call from the frontend in this project is, that they are defined in the api/index and passed from the Dashboard.tsx to the components.
The save collection call in the the collection panel is not doing that.

yaade/client/src/components/collectionPanel/CollectionPanel.tsx

Lines 55 to 64 in 0c83d78

	const handleSaveCollection = async () => {
	try {
	const response = await fetch(BASE_PATH + 'api/collection', {
	method: 'PUT',
	headers: {
	'Content-Type': 'application/json',
	},
	body: JSON.stringify(currentCollection),
	});
	if (response.status !== 200) throw new Error();

[jonrosner]

We'll have to consider how to structure the project best when we want to introduce the command palette. Basically all "actions" a user can take (like clicking a button) will have to be defined way up in the hierarchy in some kind of "command" component. This will also include the save collection action.