Optional calculation of bulk statistics in feature detection on raw input (before smoothing)

[JuliaKukulies]

Addresses #440 and allows for the user to choose whether the bulk statistics in the feature detection are calculated on the unsmoothed or the smoothed input data.

• Have you followed our guidelines in CONTRIBUTING.md?
• Have you self-reviewed your code and corrected any misspellings?
• Have you written documentation that is easy to understand?
• Have you written descriptive commit messages?
• Have you added NumPy docstrings for newly added functions?
• Have you formatted your code using black?
• If you have introduced a new functionality, have you added adequate unit tests?
• Have all tests passed in your local clone?
• If you have introduced a new functionality, have you added an example notebook?
• Have you kept your pull request small and limited so that it is easy to review?
• Have the newest changes from this branch been merged?

[codecov]

Codecov Report

Attention: Patch coverage is 83.33333% with 2 lines in your changes missing coverage. Please review.

Project coverage is 60.99%. Comparing base (3609a59) to head (132ea24).
Report is 36 commits behind head on RC_v1.5.x.

Files with missing lines	Patch %	Lines
tobac/feature_detection.py	77.77%	2 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##           RC_v1.5.x     #449      +/-   ##
=============================================
+ Coverage      60.96%   60.99%   +0.02%     
=============================================
  Files             23       23              
  Lines           3548     3553       +5     
=============================================
+ Hits            2163     2167       +4     
- Misses          1385     1386       +1     

Flag	Coverage Δ
unittests	60.99% <83.33%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Linting results by Pylint:

Your code has been rated at 8.73/10 (previous run: 8.73/10, +0.00)
_{The linting score is an indicator that reflects how well your code version follows Pylint’s coding standards and quality metrics with respect to the RC_v1.5.x branch.
A decrease usually indicates your new code does not fully meet style guidelines or has potential errors.}

[JuliaKukulies]

Tests should be OK after merge of #451

[JuliaKukulies]

Something is going on with the formatting although I seem to use a compatible black version but I had some issue with pre-commit. Will figure it out soon hopefully!

[freemansw1]

Thanks for the work on this, @JuliaKukulies . The one test failing isn't a concern.

[JuliaKukulies]

OK, so merge ? :)