Add more integration tests to the GDScript test suite

This also fixes a typo in the `bitwise_float_right_operand.gd` test.

modules/gdscript/tests/scripts/parser/errors/brace_syntax.gd

@@ -0,0 +1,3 @@
+func test() {
+	print("Hello world!");
+}

modules/gdscript/tests/scripts/parser/errors/brace_syntax.out

@@ -0,0 +1,2 @@
+GDTEST_PARSER_ERROR
+Expected ":" after function declaration.

modules/gdscript/tests/scripts/parser/errors/invalid_escape_sequence.gd

@@ -0,0 +1,2 @@
+func test():
+	var escape = "invalid escape \h <- here"

modules/gdscript/tests/scripts/parser/errors/invalid_escape_sequence.out

@@ -0,0 +1,2 @@
+GDTEST_PARSER_ERROR
+Invalid escape in string.

modules/gdscript/tests/scripts/parser/errors/invalid_ternary_operator.gd

@@ -0,0 +1,5 @@
+func test():
+	var amount = 50
+	# C-style ternary operator is invalid in GDScript.
+	# The valid syntax is `"yes" if amount < 60 else "no"`, like in Python.
+	var ternary = amount < 60 ? "yes" : "no"

modules/gdscript/tests/scripts/parser/errors/invalid_ternary_operator.out

@@ -0,0 +1,2 @@
+GDTEST_PARSER_ERROR
+Unexpected "?" in source. If you want a ternary operator, use "truthy_value if true_condition else falsy_value".

modules/gdscript/tests/scripts/parser/errors/vcs_conflict_marker.gd

@@ -0,0 +1,13 @@
+# The VCS conflict marker has only 6 `=` signs instead of 7 to prevent editors like
+# Visual Studio Code from recognizing it as an actual VCS conflict marker.
+# Nonetheless, the GDScript parser is still expected to find and report the VCS
+# conflict marker error correctly.
+
+<<<<<<< HEAD
+Hello world
+======
+Goodbye
+>>>>>>> 77976da35a11db4580b80ae27e8d65caf5208086
+
+func test():
+	pass

modules/gdscript/tests/scripts/parser/errors/vcs_conflict_marker.out

@@ -0,0 +1,2 @@
+GDTEST_PARSER_ERROR
+Unexpected "VCS conflict marker" in class body.