Make the log level back to warning for unclassified exc

[hu-dabao]

What does this PR do?

Make the log level back to warning for unclassified exceptions.
The issue was made in this commit

There are three reasons why we need to change the log level back:

1. It was at warning level, but the commit above make it to debug without explanation.
2. It is helpful to make unclassified exceptions to warning as these exceptions would be critical.
3. We don't need to set the log level back to debug, restart minion, rerun/reproduce the module calls, etc. , troubleshoot the issue, make the log level back to what it was again and restart salt-minion again.
4. Especially for salt-api calls, the salt service owner may not be able to reproduce the salt-api call easily with confidence.
5. Back to warning level will be consistent with line

What issues does this PR fix or reference?

Previous Behavior

When I see "The minion function caused an exception" in the log and I want to debug on, I have to do the following:

1. set the log level back to debug
2. restart minion
3. rerun/reproduce the module calls, etc.
4. troubleshoot the issue
5. set the log level back to what it was
6. restart minion

New Behavior

I just need to do one step: troubleshoot the issue.

Tests written?

No

Please review Salt's Contributing Guide for best practices.

[cachedout]

I think this is very reasonable. What do you think, @s0undt3ch ?

[s0undt3ch]

Instead of True use the log level you wish the traceback to be shown at, if I understand correctly, logging.WARNING or instead of exc_info_on_loglevel pass exc_info=True.

[s0undt3ch]

Oh, and yes, this is reasonable.

[hu-dabao]

Addressed in the latest commit. Thanks for pointing this out.

[hu-dabao]

@cachedout
Hi there,

I addressed @s0undt3ch 's comment by the latest commit. Should be good to merge.
Let me know if you guys have any other questions.

Thanks

[cachedout]

Thanks very much @hu-dabao !