Add provider-list tool to dump the names of the required provider family packages

[ulucinar]

Description of your changes

Depends on:

• Add two pre-processor functions for new family provider migration #117
• Add support for category-based manifest pre-processors crossplane/upjet#212

This PR adds the provider-list tool that can be used to dump the names of the required provider family (service-scoped provider) packages that satisfy:

• All managed resources and Crossplane Compositions observed in a cluster, or
• All Crossplane Compositions observed in the source tree of a Crossplane Configuration package.

Only managed resources belonging to one of the official monolithic providers with available families (i.e., upbound/provider-{aws,gcp,azure}) are considered.

Usage: provider-list --regorg="xpkg.upbound.io/upbound" --family-version=STRING <command>

Upbound provider families package dependency listing tool

Commands:
  local
  cluster

Flags:
  -h, --help                                Show context-sensitive help.
      --regorg="xpkg.upbound.io/upbound"    <registry host>/<organization> for the provider family packages.
      --family-version=STRING               Version of the provider family packages.

Run "provider-list <command> --help" for more information on a command.

Usage: provider-list local --regorg="xpkg.upbound.io/upbound" --family-version=STRING --path=STRING

Flags:
  -h, --help                                Show context-sensitive help.
      --regorg="xpkg.upbound.io/upbound"    <registry host>/<organization> for the provider family packages.
      --family-version=STRING               Version of the provider family packages.

      --path=STRING                         Source directory for the Crossplane Configuration package.

Usage: provider-list cluster --regorg="xpkg.upbound.io/upbound" --family-version=STRING

Flags:
  -h, --help                                Show context-sensitive help.
      --regorg="xpkg.upbound.io/upbound"    <registry host>/<organization> for the provider family packages.
      --family-version=STRING               Version of the provider family packages.

      --kubeconfig=STRING                   Path to the kubeconfig to use.

I have:

• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Both the local and cluster subcommands have been tested in tandem with crossplane/upjet#212 & #117. Sample runs are as follows:

> provider-list local --family-version v0.37.0 --path ./upbound/platform-ref-gcp/package

xpkg.upbound.io/upbound/provider-gcp-cloudplatform:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-compute:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-container:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-servicenetworking:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-sql:v0.37.0

> provider-list cluster --family-version v0.37.0

xpkg.upbound.io/upbound/provider-aws-rds:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-cloudplatform:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-compute:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-servicenetworking:v0.37.0
xpkg.upbound.io/upbound/provider-gcp-sql:v0.37.0

[sergenyalcin]

Thanks @ulucinar LGTM!