Use explicit output requirement file to test the exact output

[atugushev]

When a test asserts the exact content of the output requirement file make sure it uses the output file not stderr, otherwise the test will fail when something appears in stderr (e.g., a warning).

Addresses #1724 (comment).

Contributor checklist

• Provided the tests for the changes.
• Assure PR title is short, clear, and good to be included in the user-oriented changelog

Maintainer checklist

• Assure one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
• Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

[atugushev]

Thanks @ssbarnea!