Normalize node paths in errors

[Mingun]

After this change all paths in errors will point to existing nodes in KSY file and node, where error is originated

This PR introduces 10 new failures (76 vs 66) because it changes error messages which is it purpose. So, this PR should be merged together with kaitai-io/kaitai_struct_tests#92 which is fixes test data accordingly.

[Mingun]

@GreyCat, @generalmimon, I see that you have some activity in the project recently. Could you find a time to review my PRs, for example, this?

[GreyCat]

Merging this one as well! Thanks so much for cleaning this up and being persistent with all these rebasing!

[generalmimon]

I accidentally left this comment "pending" the whole time and forgot about it, so I'm at least posting it now.

[generalmimon]

I'm skeptical that only the type key is always the culprit of ParseException because fromYaml2 method processes a lot of keys inside.

Upon further inspection, these should be the calls that may emit Expressions.ParseException:

kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala

Line 190 in 3a4a0e3

val valid = srcMap.get("valid").map(ValidationSpec.fromYaml(_, path ++ List("valid")))

kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala

Lines 214 to 216 in 3a4a0e3

	DataType.fromYaml(
	None, path, metaDef, yamlAttrArgs
	)

kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala

Lines 220 to 222 in 3a4a0e3

	DataType.fromYaml(
	Some(simpleType), path, metaDef, yamlAttrArgs
	)

But even if it's always the type key, exceptions should be definitely handled closer to where they arise. Quite a few keys processed in fromYaml2 need to parse expressions, but they normally catch it right away (as they should), e.g.:

kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/ProcessExpr.scala

Lines 39 to 42 in 8913518

	} catch {
	case epe: Expressions.ParseException =>
	throw KSYParseError.expression(epe, path)
	}

• kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala

  Line 179 in 3a4a0e3

  val size = ParseUtils.getOptValueExpression(srcMap, "size", path)

• kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/ParseUtils.scala

  Lines 97 to 104 in 3a4a0e3

  	def getOptValueExpression(src: Map[String, Any], field: String, path: List[String]): Option[Ast.expr] = {
  	try {
  	getOptValueStr(src, field, path).map(Expressions.parse)
  	} catch {
  	case epe: Expressions.ParseException =>
  	throw KSYParseError.expression(epe, path ++ List(field))
  	}
  	}

kaitai_struct_compiler/shared/src/main/scala/io/kaitai/struct/format/AttrSpec.scala

Lines 291 to 296 in 3a4a0e3

	try {
	Expressions.parse(condition) -> condType
	} catch {
	case epe: Expressions.ParseException =>
	throw KSYParseError.expression(epe, casePath)
	}

[Mingun]

I'm skeptical that only the type key is always the culprit of ParseException because fromYaml2 method processes a lot of keys inside.

That does not matter. You already inside type key here, and all other keys that fromYaml2 processes here are subkeys of a type.