Provide an auto-upgrade option / migration tool for pylint configurations

[Pierre-Sassoulas]

Current problem

There are breaking changes that could impact the configuration file and make our live as maintainer easier. Asking the user to upgrade their configuration files make most breaking chance impossible. I we can upgrade the configuration file automatically it's easier to make the configuration consistent and easier to maintain. For example a migration to pyproject.toml only instead of maintaining setup.cfg, pylintrc (ini) and pyrpoejct.toml.

Desired solution

New subcommand pylint --auto-upgrade-conf to upgrade the configuration file.

Additional context

#4741 (comment)

The new framework for configuration file would help to implement this greatly, we would add an auto-upgraded expected result.

[Talador12]

#5465 mentions two examples that could be fixed by the above command. Definitely worth including these terminology updates as part of the --auto-upgrade-conf option

[Pierre-Sassoulas]

The auto-upgrade should remove pylint messages that do not exists anymore, or that can't be raised for interpreter below py-version from disable/enable.