Proper handling of user defined functions named as some standard library function

User defined function that are named the same as RetDec-recognized standard library functions will confuse the decompilation. E.g. decompilation of this binary [test.zip](https://github.com/avast-tl/retdec/files/1700427/test.zip) compiled from:
```c
void printf() {
puts("hello");
}

int main(int argv, char *argc[]) {
printf();
return 0;
}
```
May produce something like this:
```c
// ------------------------ Functions -------------------------

// Address range: 0x80483a0 - 0x80483ae
int main(int argc, char ** argv) {
// entry
int32_t * format;
printf((char *)&format);
return 0;
}

// --------------- Statically Linked Functions ----------------

// int printf(const char * restrict format, ...);
```
This should be handled better:
- Such functions should not be automatically marked as statically linked.
- Type information should not be applied only based on the function name.

The problem is, that the current behavior is oftentimes ok and greatly improve the output quality. We will need to find some good compromise.

Start with the attached test binary and the C example that defines printf, then trace the standard-library recognition and type-application paths. Done means user-defined functions are not automatically marked as statically linked or typed solely from their names, while valid standard-library recognition still preserves output quality.

Written by the indexing model from the issue text.