Provide the full parsed config file to each plugin

Feature

Provide the full parsed config file to each plugin

Pitch

Currently, Mypy plugins are passed only the Options object in their constructor, which captures Mypy options but not Mypy plugin options. Consequently, each plugins has to re-parse the file. This is a waste of time, may add to the necessary dependencies for a plugin with configuration, and requires re-implementing the logic for parsing different file types (TOML vs config). Here's an example of the pydantic plugin doing just this:

https://github.com/pydantic/pydantic/blob/06448aa41764d0c1e1c2f9455b108c4b21012929/pydantic/v1/mypy.py#L239-L256

The neatest solution would be to pass the full config object to the constructor. Unfortunately, this would be a breaking change to the constructor signature, so probably the more palatable option would be to store the config options within each Plugin instance (in the constructor), which the subclasses can use if they want:

class SomeMypyPlugin(Plugin):
    def __init__(self, options: Options) -> None:
        super().__init__(options)
        my_config_option = self.raw_config["tools"]["some_mypy_plugin"]
        # use my_config_option

Parti dal costruttore di Plugin e dal percorso di caricamento della configurazione, quindi confronta l’esempio di plugin pydantic collegato nell’issue. Traccia come vengono attualmente analizzati Options e la configurazione del plugin e definisci il completamento come la disponibilità dell’intera configurazione analizzata per le istanze del plugin, senza richiedere a ogni plugin di analizzare nuovamente file TOML o di configurazione.