v: remove dump() calls inside the compiler itself (make bootstrapping of dump() implemented before cgen easier)

Author: spytheman

vlib/v/markused/markused.v

@@ -462,7 +462,7 @@ pub fn mark_used(mut table ast.Table, mut pref_ pref.Preferences, ast_files []&a
 	}
 
 	if 'debug_used_features' in pref_.compile_defines {
-		dump(table.used_features)
+		eprintln('> debug_used_features: ${table.used_features}')
 	}
 
 	mut walker := Walker.new(

vlib/v/scanner/scanner.v

@@ -567,9 +567,9 @@ fn (mut s Scanner) end_of_file() token.Token {
 		s.line_nr--
 		if s.file_path == internally_generated_v_code {
 			// show a bit more context for that case, since the source may not be easily visible by just inspecting a source file on the filesystem
-			dump(s.text#[0..50])
-			dump(s.text#[-50..])
-			dump(s.text.len)
+			eprintln('> internally_generated_v_code, start: ${s.text#[0..50]}')
+			eprintln('> internally_generated_v_code,   end: ${s.text#[-50..]}')
+			eprintln('> internally_generated_v_code,   len: ${s.text.len}')
 		}
 		panic(
 			'the end of file `${s.file_path}` has been reached ${s.max_eofs} times already, the v parser is probably stuck.\n' +