AllureIssue and AllureTMS annotations will not build up the full URL by getting allureConfig.json

[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)

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

#### What is the current behavior?

The linkage to the issue tracker/TMS is not properly established, even though the full URL with parameterization has been set up in the Allure configuration JSON. It takes local host URL instead and throws 404 error



#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

1. Add the following details in allureConfig.json file

{
"allure": {
"directory": "allure-results",
"links": [
"https://github.com/nunit/docs/issues?utf8=✓&q={issue}",
"https://example.org/{tms}",
"{link}"

],
"brokenTestData": [
"System.Exception"
]
}
}

2. Add following annotation under test case level

```
[AllureIssue("ISSUE-123")]
[AllureTms("TMS-123")]

```

3. After executing the test case, please validate by clicking or inspecting the hyperlink generated during the build.

#### What is the expected behavior?
Users should be able to navigate to the link generated from the allureConfig.json file by clicking upon the link through the report it self

#### What is the motivation / use case for changing the behavior?
Since this feature previously worked and has encountered issues in the interim, I would like to revert it back to its previous working state.

#### Please tell us about your environment:

- Allure version: 2.11.0
- Test framework: selenium c#
- Allure adaptor: Allure.NUnit (2.11.0)
- Generate report using: .net 6

#### Other information

[//]: # (
Other NuGet Packages using in the framework

```

```

)

Start by reproducing the issue with Allure.NUnit 2.11.0 on .NET 6 using the provided allureConfig.json links and the AllureIssue and AllureTms annotations. Inspect how configured link templates are loaded and applied, then verify that the generated report hyperlinks use the configured full URLs rather than localhost and no longer return 404.

Written by the indexing model from the issue text.