Investigate leaking resources in tests

[LizardWizzard]

In this PR I tried to enable pytest to treat warnings as errors and it turns out we have significant amount of resource warnings related to resources (most commonly sockets) which are not closed properly

@bayandin pointed out that pytest 7.1 introduces a way to trace this warnings to a point where resource was allocated. See: pytest-dev/pytest#9644 Because otherwise you have to guess what is causing the warning