Enable Param Passing to Dependencies

Nobody has claimed this yet.

# Overview
Currently, dependencies install using default everything. However, chocolatey allows passing parameters to dependencies by coupling two command-line arguments: `--params-global` and `--params` (syntax `--params '/PARAM1:value1 /PARAMFLAG'`).

As an example, say `fake-package.vm` had a dependency that could be configured to use a specific port, installation path, and verbosity flag, we would pass these parameters as below:

```
choco install fake-package.vm --params-global --params '/Port:82 /InstallationPath:""C:\blah\folder with space"" /DEBUG'
```

To enable this, we need to do the following:

- [ ] Update `config.xml` with dependency parameters
- E.g., ``
- [ ] Update `flarevm.installer.vm` to check the `config.xml` for parameters and pass them accordingly during the install call
- [ ] Update each package that uses dependency parameters (mainly aimed at metapackages) to use `Get-PackageParameters` and handle any parameters as necessary (e.g., installing to a non-default dependency location specified by the "shim path" we have users provide)

# Resources
- https://docs.chocolatey.org/en-us/guides/create/parse-packageparameters-argument
- https://docs.chocolatey.org/en-us/create/functions/get-packageparameters

Start with config.xml and flarevm.installer.vm to trace how dependency entries are read and how installation calls are built. Review Chocolatey’s Get-PackageParameters guidance, then inspect the packages and metapackages that use dependency parameters. Done means configuration, installer forwarding, and package-side parameter handling are updated across the listed cases.

Written by the indexing model from the issue text.