feat(rest-assured): add support for headers blacklist

[antonfilichkin]

Context

RestAssured from version 4.2.0 added possibility to blacklist headers in the request or response logs. This adds a configurable option to consider blacklisted headers from the RestAssured LogConfiguration and blacklist them in the Allure report as well. Enabled by default, so if there is a need to expose header blacklisted by RestAssured in Allure report it must be set explicitly. This makes Allure report to blacklist the same headers.

Example of header blacklisted in Allure report:

Checklist

• [x] Sign Allure CLA
• [x] Provide unit tests

[baev]

Meanwhile, I don't like the used wording (blacklist and blacklisted). Now, most software uses allowlist and denylist instead. However, this is the exact copy of the behaviour from RestAssured, and I don't see any point to introduce additional UX complications for RestAssured users.

[baev]

@antonfilichkin thanks!