Improvement: Add Custom Data to the Environment Section of Allure, using config

[wurzelkuchen]

Quick Description

Allure provides the feature to add additional data to the environment box on the dashboard. Currently we store the neodymium version there as default, but adding additional data here has to be done by altering a file content which is not super nice.

We already have a function to add data on the fly: AllureAddons.addEnvironmentInformation(). But this would need changes in the test code, or some self build set up, if the environment should be changed.
To tackle this we should add the possibility to add environment data by using our property config. This way the data could be changed from outside for example by setting data in a build pipeline.

User Stories

As a test automation engineer,
I want to add environment data to the allure report using the configuration
so that I can see additional data about which environment the test ran upon without touching the code or the repository

Functional Requirements

• Add the possibility to configure custom values to be added to the neodymium.properties.
• The properties should be look like: neodymium.report.environment.custom.myValue = myKey
• The properties should be added to the allure report automatically using myValue and myKey (as taken from the example above) as key and value.
• This should work with properties variable replacments (see below).
• Add some of our base values as an example in our provided neodymium.properties:
  neodymium.report.environment.custom.baseURL = ${neodymium.url}
neodymium.report.environment.custom.baseURL = ${neodymium.locale}
• This should work like our normal properties and look in different sources in the following order:

1. System Environment Variables (NOTE: this is an "if possible" option, it might be difficult to achieve this)
2. System Properties
3. dev-neodymium.properties
4. neodymium.properties

NOTE: this feature is probably not compatible with the owner framework we use. But we have some similar logic in our XLTProperties in the method getPropertiesForKey.

Documentation Requirements

• Add a quick documentation for this feature to the Reports page in the wiki.

Test Requirements

• Do a smoke test using an external test suite like neodymium example

[georgkunze]

Documentation done. Code is ready for Review. i added the example lines to the neodymium example project in a corresponding branch.