Add support for Cucumber-JVM 3

[noronhaa]

[//]: # (
. Thank you so much for sending us a pull request!
.
. Make sure you have a clear name for your pull request.
. The name should start with a capital letter and no dot is required in the end of the sentence.
. To link the request with isses use the following notation: (fixes #123, fixes #321)
.
. An example of good pull request names:
. - Add Russian translation (fixes #123)
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)

Context

• Created a separate module for an Allure Cucumber-JVM 3 Listener (allure-cucumber3-jvm).
• Uses same classes from allure-cucumber2-jvm but has a cucumber-core and cucumber-java version 3.0 dependency instead.
• Where appropriate all depreciated or no longer existing methods (as of version 3.0) have been removed in favour of casting as outlined in the cucumber docs.
• Produces an identical report to using allure-cucumber2-jvm with Cucumber-JVM 2.

Usage:

• Add Dependency (only from local build at the moment)

    <dependency>
      <groupId>io.qameta.allure</groupId>
      <artifactId>allure-cucumber3-jvm</artifactId>
      <version>2.7-SNAPSHOT</version>
    </dependency>

• Add plugin to cucumber runner:

    plugin = {"io.qameta.allure.cucumber3jvm.AllureCucumber3Jvm"},

Checklist

• Sign Allure CLA
• Provide unit tests (same tests present as in allure-cucumber2-jvm for comparison)

[baev]

LGTM in general

[baev]

do not use wildcard imports

[baev]

lets make it package private or move to internal package

[baev]

make sure all the files ends with new line

[noronhaa]

Added requested changes

[baev]

@letsrokk could you please review this?

@noronhaa you may need to specify your git emails in Github profile in order to link the commits to it

[letsrokk]

@baev @noronhaa looks good to me in general

Although I do have suggestion for future improvement/refactoring - we need to think on how we can reduce code duplication here as I can see that some helper and utils classes were just copied for new adapter

Maybe we can introduce common shared module with such classes etc., but scope of this changes should be outside this PR. I'll have a look at it when we will have hands on new major Allure 3 version

[baev]

@noronhaa @letsrokk thanks!