Rename jerry_port_print_char to jerry_port_string_print for printing UTF8 directly

[lygstate]

Use name jerry_port_string_print to consistence with jerry_string_print.
Add API jerry_string_iterate_code_point and jerry_code_point_print to be called by jerry_port_string_print

Followup of #4829

JerryScript-DCO-1.0-Signed-off-by: Yonggang Luo [email protected]

[rerobika]

If i get it right there was no agreement in #4829 about dropping jerry_port_print_char, rather than it should be kept but we can introduce jerry_port_string_print for convenience.
However @dbatyai is currently working on this topic, so be patient.

[lygstate]

If i get it right there was no agreement in #4829 about dropping jerry_port_print_char, rather than it should be kept but we can introduce jerry_port_string_print for convenience. However @dbatyai is currently working on this topic, so be patient.

hi we have jerry_code_point_print do the same thing, anyway, I am looking on it

[dbatyai]

As I've said, and as @rerobika pointed out, this is not the right approach, jerry_port_print_char should not be removed, and jerry_code_point_print is not the same. I also don't see any reason to introduce the concept of code points to the api.

Also, as I've said before, I'm making a lot of changes to the entire port infrastructure, including how i/o is handled in jerry-ext and jerry-main, among many other things, and the changes present here are already incompatible. I do not wan't to merge anything that I would have to rewrite entirely in the next api revision patch, there's no reason for it.

Also, the debugger and port api interaction needs more thought to it than just slamming in new api functions.

I will introduce a port function for printing strings in my next patch soon, please be patient.

[lygstate]

@dbatyai
That's sounds very good, I am looking for it.