set settings logger with debug instead of warning

[AurelienJaquier]

Description

Motivation: Overall I don't this this should be a warning, a simple debug statement is enough. There are a lot of stuff that are not defined in settings, but can be set as such (stim_start, stim_end, stimulus_current, etc.), this is something expected.

BluePyEModel sets stimulus_current, sometimes even stim_start, stim_end, and I see this warning a lot

Checklist:

• Unit tests are added to cover the changes (skip if not applicable).
• The changes are mentioned in the documentation (skip if not applicable).
• CHANGELOG file is updated (skip if not applicable).

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.80%. Comparing base (2cddd26) to head (2b368fd).
Report is 14 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #392      +/-   ##
==========================================
+ Coverage   91.73%   91.80%   +0.07%     
==========================================
  Files          36       37       +1     
  Lines        6278     6956     +678     
  Branches     2033     2245     +212     
==========================================
+ Hits         5759     6386     +627     
- Misses        266      298      +32     
- Partials      253      272      +19     

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

[ilkilic]

Yes I agree