Stop spamming System.Net.Http.Tests output with HTTP/2 skipped tests (#35913)
There are a bunch of tests that don't make sense on HTTP/2, but end up executing because of how our tests are structured. As a result, the test itself checks whether HTTP/2 is applicable and bails if it isn't. Currently some of these are bailing by throwing a SkipTestException, which results in a message being output on the console. Such messages are meant for tests that can be run in some circumstances, e.g. a stress test that needs an environment variable set. They aren't needed when a test is never going to run.
I also marked the stress tests as outerloop so they don't spam the console when just running innerloop.