Should pygame.base.get_warnings_filter/pygame.base.set_warnings_filter be public API (likely not)?
Current idea of warning priorities (can be changed):
0 is the most impactful - if a warning of its type is triggered, probably the code won't work
1 is less severe - like deprecation warnings
2 is least important - warnings might be pedantic or about conventions or detection of common pitfalls that can contain false positives, so is suppressed by default
This PR does not introduce new warnings to guide users, only sets up a system for filtering them. Porting pygame/pygame#1682 or implementing something like that is still needed, but in a separate PR.
Fixes #2894
Notes ~(mostly to self)~:
pygame.base.get_warnings_filter/pygame.base.set_warnings_filterbe public API (likely not)?