Add openfeign module

[sbushmelev]

Add new module that automatically captures Feign client HTTP traffic as Allure attachments for comprehensive API test reporting.

[CLAassistant]

All committers have signed the CLA.

[baev]

Good job! 👍

[baev]

allure-openfeign?

[baev]

tear down?

[baev]

use AssertJ assertions instead

[baev]

Don't use assertTrue, AssertJ provides more convenient ways to check that

[baev]

Since it's only a few tests, we can use @BeforeEach instead?

[baev]

Please, add tests for the plan body response and no response body

[baev]

check not only the attachment name, but the body as well

[sbushmelev]

Hello! When writing additional tests, I discovered a nuance. If you need to use the feign.Response entity in an autotest, for example, to get the headers, the feign.codec.Decode#decode method is not called, which makes sense since the attachment is not attached. Using feign.ResponseInterceptor is not possible because the feign.Response that is passed to the feign.ResponseInterceptor#intercept method is designed so that you can only read the response body once. However, since openFeign supports multiple http clients, you can use the following construct:

        HttpClientBuilder builder = HttpClientBuilder.create()
                .addInterceptorFirst(new AllureHttpClientRequest())
                .addInterceptorLast(new AllureHttpClientResponse());

        Example example = Feign.builder()
                .client(new ApacheHttpClient(builder.build()))
                .decoder(new GsonDecoder())
                .encoder(new GsonEncoder())
                .logLevel(Logger.Level.FULL)
                .target(Example.class, "http://example.com/");

I have tested it locally and it works both when the interface method returns feign.Response and when the DTO.If it makes sense, I can write tests for all the http clients that openFeign supports, and update the README with examples of how to use openFeign