Better algorithm for collecting information from large output

[permcody]

So we are running into a build issue where there are over 5MBs of output warnings obscuring what we think is a real error somewhere at the end of the build process. However we can't see the end. Here's the link to the output:
https://civet.inl.gov/job/512435/

Here's what the end of the long part of the log looks like:

/opt/moose/miniconda/include/boost/math/special_functions/lanczos.hpp:927:10: warning: non-standard suffix on floating constant [-Wpedantic]
  927 |          static_cast<T>(BOOST_MATH_BIG_CONSTANT(T, 64, 2223966599737.814969312127353235818710172)),
      |          ^~~~~~~~~~~
In file included from /opt/moose/miniconda/include/boost/math/special_functions/gamma.hpp:30,
                 from /opt/moose/miniconda/include/boost/math/special_functions/beta.hpp:15,
                 from /opt/moose/miniconda/include/boost/math/distributions/beta.hpp:28,
                 from /opt/moose/miniconda/include/boost/math/distributions.hpp:17,
                 from /opt/civet/build_0/moose/modules/stochastic_tools/build/header_symlinks/BoostDistribution.h:17,
                 from /opt/civet/build_0/moose/modules/stochastic_tools/build/header_symlinks/BoostNormalDistribution.h:12,
                 from /opt/civet/build_0/moose/modules/stochastic_tools/build/header_symlinks/PolynomialQuadrature.h:17,
                 from /opt/civet/build_0/moose/modules/stochastic_tools/src/utils/PolynomialQuadrature.C:10,
                 from /opt/civet/build_0/moose/modules/stochastic_tools/build/unity_src/utils_Unity.C:4:
/opt/moose/miniconda/include/boost/math/special_functions/lanczos.hpp:928:10: warning: non-standard suffix on floating constant [-Wpedantic]
  928 |          static_cast<T>(BOOST_MATH_BIG_CONSTANT(T, 64, 856940834518.9562481809925866825485883417)),
      |          ^~~~~~~~~~~
In file included from /opt/moose/miniconda/include/boost/math/special_functions/gamma.hpp:30,
                 from /opt/moose/miniconda/include/boost/math/special_functions/beta.hpp:15,
                 from /opt/moose/miniconda/include/boost/math/distributions/beta.hpp:28,
                 from /opt/moose/miniconda/include/boost/math/distributions.hpp:17,
                 from /opt/civet/build_0/moose/modules/stochastic_tools/build/header_symlinks/BoostDistribution.h:17,


*****************************************************

CIVET: Output size exceeded limit (5242880 bytes), further output will not be displayed!

*****************************************************

It would be handy if instead of just truncating the end of the output. We do something similar to what we do in the TestHarness (i.e. we trim the middle of the output instead: https://github.com/idaholab/moose/blob/2d94d613e2077c77757b31342c7a42109f726797/python/TestHarness/util.py#L749

This would enable us to see the end of a large log.

[permcody]

Tag @dschwen, @dylanjm