Error tagging

[soxofaan]

Any reason JobNotFound is tagged with Processes?

openeo-api/errors.json

Lines 256 to 263 in 1247172

	"JobNotFound": {
	"description": "The requested job does not exist.",
	"message": "The job '{identifier}' does not exist.",
	"http": 404,
	"tags": [
	"Job Management",
	"Processes"
	]

I'm also not sure it's necessary to put FileNotFound and FileContentInvalid under Processes

openeo-api/errors.json

Lines 123 to 130 in 1247172

	"FileNotFound": {
	"description": "The requested file does not exist.",
	"message": "File '{file}' does not exist.",
	"http": 404,
	"tags": [
	"File Management",
	"Processes"
	]

openeo-api/errors.json

Lines 173 to 180 in 1247172

	"FileContentInvalid": {
	"description": "The content of the file is invalid.",
	"message": "File content is invalid.",
	"http": 400,
	"tags": [
	"File Management",
	"Processes"
	]

[m-mohr]

"Processes" in that case meant that it could be thrown from executing a process, e.g. FileNotFound if a file specified to the run_udf function is not available. Although I'm not sure it's useful, because it's probably better to use ProcessArgumentInvalid with the reason being basically what FileNotFound says. So I'll probably remove these tags completely as nowadays it's usually also specified in processes themselves.

[m-mohr]

I realized the errors.json was quite outdated and the last major update was in 0.4 so took the chance to update it, see PR #275. It should incorporate the requested changes.