allure-robotframework creates separate attachment files for log messages from each keyword

#### I'm submitting a ...
- [***] bug-feature report

#### What is the current behavior?
Currently allure-robotframework creates separate attachment files for log messages from each keyword, no matter if it is from external library or from builtin Log keyword.

#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Unfortunately can't provide any test results. I think, that it will be enough to create few tests with Log keyword to see result.

To launch test project i use this command line:
robot --listener allure_robotframework --loglevel DEBUG -T --outputdir .\log\robot --variable REMOTE_URI:127.0.0.1:1234 --console verbose -s 'List_Test' .\x-tests

#### What is the expected behavior?
I expect that all **logging** attachments for whole test project run should go in to one attachment file.

#### What is the motivation / use case for changing the behavior?
This behavior can inflict problem with accessing output folder when running complex test suites with many log messages. For example, simple test suite with two normal tests generates 84 attachment files. You may imagine what will happens with output directory when a really big test project will run few times.

#### Please tell us about your environment:

- Allure version: 2.10.0
- Test framework: Robot Framework 3.1 (Python 3.6.7 on win32)
- Allure adaptor: allure-robotframework@2.6.0

首先使用 Robot Framework 的 Log 关键字和提供的 robot --listener allure_robotframework 命令复现问题，并比较一个小型套件的附件数量。跟踪 allure_robotframework listener 对日志消息的处理。完成标准是：整个运行过程的日志附件在不丢失消息的情况下合并到一个文件中，并在更大的套件上验证该行为。

由索引模型根据 Issue 内容生成。