fix(pylint): overgeneral-exceptions fully qualified name

[gardar]

Fixes errors like this:

- MegaLinter key: [PYTHON_PYLINT]
- Rules config: [.pylintrc]
- Number of files analyzed: [6]
--Error detail:
pylint: Command line or configuration file:1: UserWarning: 'Exception' is not a proper value for the 'overgeneral-exceptions' option. Use fully qualified name (maybe 'builtins.Exception' ?) instead. This will cease to be checked at runtime when the configuration upgrader is released.

Proposed Changes

The overgeneral-exceptions option in pylint now requires a fully qualified name.
Even though this has already been fixed in the megalinter pylint docs:

megalinter/docs/descriptors/python_pylint.md

Lines 723 to 726 in 69b1261

	--overgeneral-exceptions <comma-separated class names>
	Exceptions that will emit a warning when caught.
	(default: ('builtins.BaseException',
	'builtins.Exception'))

Ps. Perhaps linter config should also be auto updated in addition to the linter docs?

Readiness Checklist

Author/Contributor

• Add entry to the CHANGELOG listing the change and linking to the corresponding issue (if appropriate)
• If documentation is needed for this change, has that been included in this pull request

Reviewing Maintainer

• Label as breaking if this is a large fundamental change
• Label as either automation, bug, documentation, enhancement, infrastructure, or performance

[echoix]

Thanks a lot!