Do not use Guava's NullOutputStream

[raul-arabaolaza]

Its location has been changed in Guava 14 meaning the tests of this plugin work fine with current baseline but fail with the PCT on the upcoming lts or when baseline is updated.

I could also wait for 2.332.1 to be released and then change the baseline and update the related Guava code, but I believe is simpler to just get rid of the related Guava usage in the test given how simple it is.

This does not affect production code but breaks any pipeline trying to run the PCT or the tests of this plugin with newer core versions

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[alecharp]

code is equivalent, looks good to me.

[basil]

Another alternative to Guava's com.google.common.io.NullOutputStream is org.apache.commons.io.output.NullOutputStream.

[jglick]

@dwnusbaum remember you need to add a category label before merging for Release Drafter, and to trigger CD if appropriate.

[jglick]

Or just ByteArrayOutputStream discarding the result.

[jglick]

you need to add a category label before merging

If you forget, you can add the label later and manually trigger the workflow on master.