feat(dev): add release:verify and repo:compliance --new-packagist-token, reorganize all commands

[bshaffer]

• release:verify: Last release we had some packages fail to be updated. This adds a script to run after our release, so that we can be notified if releases do not show up in packagist.
• repo-info --new-packagist-token: I believe the releases failed because the packagist tokens were rotated. The --update-packagist-token flag on the repo-info flag allows us to update the token across all repos at once
• fixes bugs in repo-info command, renamed to repo:compliance, better output for repo:compliance
• Reorganize all commands to use format component:update instead of component-update (for example), so that commands are organized better:

$ ./google-cloud
Available commands:
  completion                      Dump the shell completion script
  docfx                           Generate DocFX yaml from a phpdoc strucutre.xml
  help                            Display help for a command
  list                            List commands
 component
  component:add-version           Add a new version to an existing Component
  component:info                  [info] list info of a component or the whole library
  component:new                   Add a new Component
  component:update:deps           update a dependency across all components
  component:update:gencode        Update one or all components using Owlbot
  component:update:readme-sample  Add a sample to a component
 release
  release:info                    list information for a google-cloud-php release
  release:verify                  Verifies the package version from packagist.
 repo
  repo:compliance                 ensure all github repositories meet compliance
  repo:split                      [split] Split subtree and push to various remotes.

TODO

• verify this worked on next release (it didn't work)
• add verification step to ensure new versions were added to packagist

[Hectorhammett]

I would love to make a command that locally can fix the style <3

[bshaffer]

We have a composer style-fix command in the project root, although it probably needs to be cleaned up