Provide the user more information when installing special package types

### What You Are Seeing?

We should be clearer when installing special package types (ie. hook, extension, template etc.) what is actually being done.

For example we should tell the user:

* What files are going to be placed
* Where they are going to be placed
* Explaining that this is a hook / extension / template / etc. package type.
* If the user has prompting (ie. `allowGlobalConfirmation` is off or `--yes` is not passed on the command line) then they should also be prompted to continue.

### What is Expected?

That the user is given information about what this special package type is going to do and prompt them to confirm (if they have that option).

### How Did You Get This To Happen? (Steps to Reproduce)

N/A

### System Details

N/A

### Output Log

N/A

The issue does not name a file, test, or entry point. Start by locating the installation flow for hook, extension, and template package types, then trace how allowGlobalConfirmation and --yes affect prompting. Done means the user sees the package type and destination files before installation and is asked to continue when prompting is enabled.

Written by the indexing model from the issue text.