test: ASAN leak on feedback demon call using cURL

Found that after patch set of 5 commits:

  aa97a185 ("feedback_daemon: count and report some events")
  e9c9832a ("feedback_daemon: generate report right before sending")
  bc15e0f0 ("feedback_daemon: send feedback on server start")
  670acf0d ("feedback_daemon: rename `send_test` to `send`")
  c5d595bc ("feedback_daemon: include server uptime in the report")

began to leak feedback demon on using cURL. To avoid of it decided to
add LSAN suppresions:

  1. for /lib/x86_64-linux-gnu/libcrypto.so
     leak:libcrypto.so*
  2. for /lib/x86_64-linux-gnu/libssl.so
     leak:libssl.so*

Needed for tarantool/tarantool-qa#116

asan/lsan.supp

@@ -8,6 +8,13 @@
 # source: /usr/lib/x86_64-linux-gnu/libcrypto.so
 leak:CRYPTO_zalloc
 
+# test: all (feedback demon fails using cURL)
+# https://github.com/tarantool/tarantool-qa/issues/116
+# source: /lib/x86_64-linux-gnu/libcrypto.so
+leak:libcrypto.so*
+# source: /lib/x86_64-linux-gnu/libssl.so
+leak:libssl.so*
+
 # test: app-tap/http_client.test.lua
 # source: src/tarantool
 leak:Curl_setstropt