Remove jerry-libc (#2332)

Rationale:
- There is no port under targets/ that would use it. All of them
  turn it off when building.
- That's no surprise, as jerry-libc supports no barebone MCUs but
  posix targets with syscalls only. Actually, that's Linux only,
  because macOS builds have turned off the use of jerry-libc a
  while ago.
- And there is no point in maintaining a highly restricted set of
  libc functions: as soon as someone wants to use JerryScript in a
  scenario that needs more functions than jerry-main, they have to
  choose a different libc (most problably the compiler's default
  one).

I think that we should not keep supporting an otherwise unused
library for the purposes of jerry-main on arm/x86/x64-linux  only.

JerryScript-DCO-1.0-Signed-off-by: Akos Kiss akiss@inf.u-szeged.hu

targets/tizenrt-artik053/README.md

@@ -10,7 +10,7 @@ If you are in a hurry, run following commands:
 
 ```
 $ sudo apt-add-repository -y "ppa:team-gcc-arm-embedded/ppa"
-$ sudo apt-get update 
+$ sudo apt-get update
 $ sudo apt-get install gcc-arm-embedded
 $ git clone https://github.com/jerryscript-project/jerryscript.git jerryscript
 $ cd jerryscript
@@ -87,7 +87,6 @@ jerryscript/tools/build.py \
     --clean \
     --lto=OFF \
     --jerry-cmdline=OFF \
-    --jerry-libc=OFF \
     --all-in-one=OFF \
     --mem-heap=70 \
     --profile=es2015-subset \
@@ -151,4 +150,4 @@ Without argument it prints:
 TASH>>jerry                                                                        
 No input files, running a hello world demo:                                        
 Hello World from JerryScript
-```
+```