supp: Ignore leaks caused by shout/sethostent

sethostent() seems to be using a global state and we endup with leaks from
that API when called through shout_init(). We had the option to only
ignore the shout case, but the impression is that if we have shout and
another sethostend user, as it's a global state, we may endup with a
different stack trace for the same leak. So in the end, we just ignore
memory allocated by sethostent in general.
24 jobs for shout-sethostend-leak in 150 minutes and 8 seconds (queued for 2 seconds)
Status Job ID Name Coverage
  Preparation
passed #336904
gst indent

00:00:22

passed #336903
manifest

00:00:27

 
  Build
passed #336905
build fedora x86_64

00:13:40

passed #336906
build nodebug fedora x86_64

00:25:25

passed #336907
build static fedora x86_64

00:37:42

passed #336908
build static nodebug fedora x86_64

00:39:33

 
  Test
passed #336909
check fedora

00:03:42

passed #336910
integration testsuites fedora

00:13:19

 
  Full Builds
passed #337128
build cerbero android universal

00:34:51

passed #337130
build cerbero cross win32

00:06:23

passed #337129
build cerbero cross win64

00:04:35

passed #336911
build cerbero fedora x86_64

00:22:44

failed #336912
build cerbero android universal

00:17:10

failed #336913
build cerbero cross win32

00:07:01

failed #336914
build cerbero cross win64

00:06:27

 
  Full Tests
passed #336916
valgrind bad

00:04:15

passed #337305
valgrind ges

00:04:23

passed #337325
valgrind good

00:20:33

failed #336917
valgrind ges

00:14:49

passed #337307
valgrind good

00:09:24

passed #337306
valgrind good

00:06:15

passed #336915
valgrind good

00:26:42

 
  Apps
passed #336918
android universal examples

00:06:20

 
  Deploy
passed #336919
documentation

00:03:38