Configured maximum stack trace depth is not always honored

[JcolemanNR]

Description
While running the unit tests in debug (not an intended configuration), I noticed a unit test failure with how stack depth is managed. While switching to release configuration does allow the unit tests to pass, there is actually some erroneous logic in how we reduce stack traces.

For example, even the release configuration test asks for a max stack depth of 3, but is satisfied when only 2 are returned despite there being over 40 stack frames that aren't from 'NewRelic' assemblies.

Expected Behavior
If there are enough non 'NewRelic' stack frames, then we should return the requested maximum stack frames.