Add all Python warnings for checking by `warning-checker` by default.

[mmcky]

Update warning checker configuration to include UserWarning

@mmcky : one for the warning checker: /home/runner/miniconda3/envs/quantecon/lib/python3.12/site-packages/IPython/core/pylabtools.py:170: UserWarning: Creating legend with loc="best" can be slow with large amounts of data. fig.canvas.print_figure(bytes_io, **kw)

Originally posted by @jstac in QuantEcon/lecture-python.myst#545 (comment)

[jstac]

Thanks @mmcky . Here's what Claude claims to be the full set of warnings:

Python has several built-in warning categories besides UserWarning. Here are the main ones:
Core Warning Types:

DeprecationWarning - For deprecated features that will be removed in future versions
PendingDeprecationWarning - For features that may be deprecated in the future
SyntaxWarning - For dubious syntax that isn't technically incorrect
RuntimeWarning - For runtime issues that aren't errors
FutureWarning - For constructs that will change semantically in the future
ImportWarning - For issues with imports
UnicodeWarning - For Unicode-related issues
BytesWarning - For issues related to bytes and buffer objects
ResourceWarning - For resource usage issues (like unclosed files)

Specialized Warnings:

EncodingWarning - For encoding-related issues (added in Python 3.10)

[mmcky]

@copilot can you please add the above Warning types to the default configuration for our actions/check-warnings action.