Fix environment variables resolution

[gabrielcarioca]

We were using a deprecated perform method without the env parameter coming from it, meaning we were not getting environment variables sent to the build from Jenkinsfile, for example.

Updated the perform and generateReport methods to inherit and use the proper environment variables set by the user.

Resolves #360

)

Testing done

I've tested it local and in our company pipeline that were failing as we couldn't set the JAVA_HOME for the allure command to run.

Before: Even though JAVA_HOME was properly set, as we can see from the logs, the execution failed

After: Properly found the JAVA_HOME sent as a parameter and created the allure report

For a pipeline we had running in linux in which we sent the jdk parameter it continued working as before.

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[baev]

could you please rebase the PR

[gabrielcarioca]

could you please rebase the PR

Done

[baev]

@gabrielcarioca thanks!