allure-robotframework not supporting link issue pattern

#### I'm submitting a ...
- [ ] bug report
- [x ] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.

#### What is the current behavior?
When creating allure results with allure-robotframework it doesn't support parameterized way for creating prefix for issue links. For example if robot test contains TAG "issue:myIssueId", allure results (and generated allure report) will contain URL into host where allure report is served (like http://10.251.83.101:65165/myIssueId).

Current workaround is to place URL into test TAG, e.g. issue:https://myJira.com/browse/myIssueId, This shows whole URL in the linkname on allure report.

#### What is the expected behavior?
Possibility to have parameterized base URL to issue tracking system that is copied in the front of issueId instead host where report is served. For example command line switch or property file that includes key-value pair like "allure.link.issue.pattern=https;//myJira.com/browse/". Then allure robotframework listener should add this value in front of issue link URL.

#### What is the motivation / use case for changing the behavior?
Generated allure report link section is more readable, when link name is shorter and URL is not shown on the report.

#### Please tell us about your environment:

- Allure version: 2.1.0
- Test framework: allure-python 2.9.43
- Allure adaptor: allure-robotframework 2.9.43

Commencez par le listener allure-robotframework qui traite les valeurs de Robot TAG et examinez la manière dont les liens d’issues sont construits. Vérifiez les points d’entrée de configuration existants via la ligne de commande ou le fichier de propriétés ; le travail est considéré comme terminé lorsqu’une URL de base configurable pour les liens d’issues préfixe un ID d’issue, tandis que le rapport affiche le nom de lien plus court.

Rédigé par le modèle d'indexation à partir du texte de l'issue.