style: Modernize object inheritance, super() calls, and OSError aliases

[echoix]

In prevision of being able to introduce some faster (and more complete) Python checks, like with using the incredibly fast ruff linter https://docs.astral.sh/ruff/, part of the rules implemented come from pyupgrade https://github.com/asottile/pyupgrade. pyupgrade helps to automatically upgrade syntax to newer versions of Python. In order to reduce the diff if we decide to start using this, I'm starting by applying only three really simple changes, that apply to any version of python past python 3.3 (released in 2012, EOL in 2017).

1. Remove useless object inheritance:
   • https://github.com/asottile/pyupgrade?tab=readme-ov-file#rewrites-class-declaration
   • https://docs.astral.sh/ruff/rules/useless-object-inheritance/
   • Since Python 3, all classes inherit from object
   • These "new-style" class are there since Python 2.2, old style class removed in Python 3
2. Simplify super() calls if the first argument is the same class, and the second is equivalent (like self)
   • https://github.com/asottile/pyupgrade?tab=readme-ov-file#super-calls
   • https://docs.astral.sh/ruff/rules/super-call-with-parameters/
   • Part of Python 3
   • Note that there are places where it wasn't changed, like

     grass/gui/wxpython/gcp/manager.py

     Lines 2368 to 2372 in 97da922

     	def OnSize(self, event):
     	"""Adjust Map Windows after GCP Map Display has been resized"""
     	# re-render image on idle
     	self.resize = grass.clock()
     	super(MapPanel, self).OnSize(event)

3. Use OSError for all other aliases of OSError.
   • https://github.com/asottile/pyupgrade?tab=readme-ov-file#oserror-aliases
   • https://docs.astral.sh/ruff/rules/os-error-alias/
   • In Python 3.3, multiple redundant errors were simplified to OSError, and the existing errors were aliased to keep working.
   • In our case, there were places where a try/catch for WindowsError was needed, and not it is simply OSError, for all platforms. Nice!

So in essence these are quite unlikely to cause serious regressions, as it is how it is supposed to work for a long time already.
The pyupgrade tool also has some filters to choose what minimum python version you want to support. After trying with --py37-plus, I started again with --py3-only and disabled the most I could. I then passed through the 300+ files to only keep these 3 changes

[echoix]

I might want some feedback on if the changes should be kept in the cgentypes folder, some of it seems like it is copied from another project. I wasn't sure if you were patching these up or it just wasn't in sync (like the lex.py file)

[nilason]

I might want some feedback on if the changes should be kept in the cgentypes folder, some of it seems like it is copied from another project. I wasn't sure if you were patching these up or it just wasn't in sync (like the lex.py file)

I'd recommend leave out any non-critical changes from python/libgrass_interface_generator/ctypesgen directory. As noted in https://github.com/OSGeo/grass/blob/main/python/libgrass_interface_generator/README.md, any patches should be reported upstreams. Changes to ctypesgen, not listed in the README file, will be null and void by next update of the package. (I see now there are actually such changes, unfortunately).

[echoix]

To revert

[echoix]

Since indeed, by definition it wasn't that essential, I reverted the changes from that folder

Changes to ctypesgen, not listed in the README file, will be null and void by next update of the package. (I see now there are actually such changes, unfortunately).

Maybe something that later could be handled in the periodic update workflow from #3200, wink wink!

[echoix]

Since all checks have passed, is still up to date, and had 2 reviews, I think it could be ready to merge ;)