Create two separate hook libraries: folder-copy, and config-manager

Nessuno ha ancora preso questa issue.

There are two different ways to manage PHPCS coding standards installation:
- You can copy the standards folder directly into phpcs's installed path, so they are just "there" for phpcs to use.
- You can actively manage the entries in phpcs's configuration file for the `installed_paths` directive, essentially informing phpcs where to find your standards in their "native" composer-installed locations.

The first method is the currently-implemented approach, but the code already exists to perform the second approach as well.

What needs to happen is this:
- Separate the two approachs out into two different classes, but that share the same public interface (making them interchangeable).
- Update the installer to check for an `extra` entry in the project's `composer.json` file that can be used as a switch to determine which method is preferred by the project (copy-folders or manage-config).
- Update the installer to use the preferred method. This should apply to both the `phpcs-coding-standard` type as well as the postInstall hooks.

Inizia dall’installer e ispeziona il codice esistente per la gestione di PHPCS installed_paths, quindi esamina come vengono gestiti phpcs-coding-standard e gli hook postInstall. Separa gli approcci copy-folders e manage-config dietro un’unica interfaccia pubblica, usa la voce extra di composer.json come selettore e verifica che entrambi i percorsi dell’installer rispettino il metodo selezionato.

Scritto dal modello di indicizzazione a partire dal testo della issue.