Option to enable breakpoints to stop when warnings are raised in the python debugger

[whentheworldfallsapart]

It would be nice if under the breakpoints drop down in the debugger if there was an option to set a breakpoints for warnings (understanding that warnings are handled completely different from exceptions in python). Numpy allows raising warnings as errors "np.seterr(all='raise')", this can be used to help locate what is causing a divide by zero warning for example. But most packages dont have this feature, and tracing down warning while looping over large sets of data can often require print statements to locate which input data is causing a warning inside a package. Having the feature in vscode debugging to add breakpoints to stop on warnings would be very helpful. (This a popular feature in MATLAB for example, allowing the user to stop on warnings).

[brettcannon]

If you want Python to raise warnings as exceptions, you can do that from the command-line with -Werror. You can also set the environment variable PYTHONWARNINGS to error.

See https://docs.python.org/3/library/warnings.html#describing-warning-filters for more details (including finer-grained control over what to do for different warnings).

[brettcannon]

Moved to #17200