fix: remove attempt to get a more comprehensive error

[martinjagodic]

Closes #7262

attempt was used to better handle the function, but it obtused the error so it was not clear which frontamtter field was duplicated.

[martinjagodic]

The collection list view now displays the error toast, but does not load any entries if one is corrupted. A fix should be somewhere in backend.ts. formattedEntries and filteredEntries should return the non-corrupted entries, but still trigger the error.

[yanthomasdev]

One small nit from me

[yanthomasdev]

My only worry is if there's a ton of errors at one time. Maybe we should aggregate it?

Also, the key is ui.toast.duplicateFrontmatterKey, but from what I understood the code will also catch other types of parsing issues, so maybe the name should be more generic? Like ui.toast.entryParseErrors

Suggested change

	response.errors?.forEach(error => {
	dispatch(
	addNotification({
	message: {
	details: error,
	key: 'ui.toast.duplicateFrontmatterKey',
	},
	type: 'warning',
	dismissAfter: 8000,
	}),
	);
	});
	if (response.errors?.length) {
	dispatch(addNotification({
	message: {
	details: response.errors.join('\n'),
	key: 'ui.toast.entryParseErrors',
	},
	type: 'warning',
	dismissAfter: 8000,
	}));
	}

[martinjagodic]

closing as this is fixed in #7679