dev: Ensure Ads and Common Protos new component parameters are derived correctly

We have a command which builds new components from proto files and calculates their parameters based on the protos provided:

```
./dev/google-cloud component:new
```

However, when a component has the namespace `Google\Ads`, custom parameters must be provided in order to configure the appropriate composer package name and github repository:

- The composer package name should use `googleapis` as the vendor instead of `google`, e.g. `googleads/[project-name]` instead of `google/[project-name]`
- The github repo should be `googleapis/php-ads-[project-name]`

The same is true for `CommonProtos` libraries - if no GAPIC clients exist, we append `CommonProtos` to the component name, and `-common-protos` to the package and repo names.

See go/cloud-sdk-php-new-component-heuristics

Start with ./dev/google-cloud component:new and trace how it derives parameters from proto files, focusing on Google\Ads and CommonProtos namespaces. Generate examples for both cases, including a CommonProtos library with no GAPIC clients, and verify that the composer package and GitHub repository names match the requested conventions.

Written by the indexing model from the issue text.