Add support for async step functions returning ValueTask

[delatrie]

I'm submitting a ...

• 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?

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

Given the following test:

using System.Threading.Tasks;
using NUnit.Framework;
using NUnit.Allure.Attributes;

class MyTestClass
{
    [Test]
    public async ValueTask MyTest()
    {
        await MyStep();

        static async ValueTask MyStep()
        {
            await Task.Delay(1000);
            throw new Exception();
        }
    }
}

The following can be observed:

• The step's status is incorrectly set to passed
• The step's duration is unexpectedly low

What is the expected behavior?

• The step's status is broken.
• The step's duration is close to 1000ms.

Please tell us about your environment:

• Allure version: 2.25.0
• Test framework: [email protected]
• Allure adaptor: [email protected]

Other information

The issue occurs because the aspect doesn't await the return value of the step in a manner similar to how it's done for steps returning Task or Task<T>. We check for Task and Task<T> explicitly, so we should add similar branches for ValueTask and ValueTask<T> (the System.Threading.Tasks.Extensions package should be used to access the types).