Path to feature file in allure report

[//]: # (
. 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 ...
- [ ] 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?

I have tests in many directories (many repos, in fact). All get run together for a report we gen in Allure.
The report shows the feature name. However, there seems to be no way to display the path to the feature file.
Because the tests are in lots of dirs - it is then rather painful to find the right file.

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

#### What is the expected behavior?

Would love for the plugin to also set the path to feature file in the allure report.

#### What is the motivation / use case for changing the behavior?

Ease of use for developers and QA folks.

#### Please tell us about your environment:

- Allure version: 2.1.0
- Test framework: pytest@3.0
- Allure adaptor: allure-pytest@2.0.0b1

#### Other information

[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)

Iniziate tracciando il modo in cui allure-pytest registra i metadati delle feature e il modo in cui il report Allure generato li visualizza. Confermate il formato previsto del percorso sorgente e verificate che un report generato da test presenti in più directory mostri il percorso di ogni file di feature.

Scritto dal modello di indicizzazione a partire dal testo della issue.