Add provider family linter

[ulucinar]

Description of your changes

This PR adds a new linter, ssop-linter, that asserts the following in all the packages in a provider family:

• Each CRD generated for a provider family is actually packaged in the expected service-scoped provider, e.g., the CRD domains.activedirectory.gcp.upbound.io should be packaged in the provider provider-gcp-activedirectory. The expected suffix for the provider is the short group name (e.g., activedirectory) of the CRD.
• Each provider has metadata (currently only v1alpha1 API level is supported for the provider metadata)
• The metadata for each provider package in the family contains the family label with key pkg.crossplane.io/provider-family and the expected value of the config package for the family, e.g., pkg.crossplane.io/provider-family: provider-family-gcp for the GCP family.
• Each provider package metadata in the family, except for the config package itself, declares a dependency to the family's config package.
• An optional check for the Upbound authentication annotation on the ProviderConfig CRD in the family's config package

❯ ./_output/bin/darwin_arm64/lint-provider-family --help
usage: ssop-linter [<flags>] <command> [<args> ...]

Linter for the official provider families

Flags:
  --help  Show context-sensitive help (also try --help-long and --help-man).

Commands:
  help [<command>...]
    Show help.

  family --provider-name=PROVIDER-NAME --provider-version=PROVIDER-VERSION [<flags>]
    Checks whether all CRDs generated for a provider family are packaged in the corresponding service-scoped provider and checks the provider metadata.

❯ ./_output/bin/darwin_arm64/lint-provider-family family --help
usage: ssop-linter family --provider-name=PROVIDER-NAME --provider-version=PROVIDER-VERSION [<flags>]

Checks whether all CRDs generated for a provider family are packaged in the corresponding service-scoped provider and checks the provider metadata.

Flags:
  --help                         Show context-sensitive help (also try --help-long and --help-man).
  --crd-dir=./package/crds       Directory containing all the generated CRDs for the provider family.
  --provider-name=PROVIDER-NAME  Provider name such as "aws".
  --provider-version=PROVIDER-VERSION  
                                 Provider family tag to check such as "v0.37.0".
  --package-repo-org="xpkg.upbound.io/upbound-release-candidates"  
                                 Package repo organization with the registry host for the provider family.
  --check-auth-annotation        Check Upbound authentication annotation on the ProviderConfig CRD in the provider family's config package.'

I have:

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

TODO:

• Let's also add an optional check for the Upbound authentication annotation on the ProviderConfig CRD in the family's config package.

How has this code been tested

Tested against the AWS, Azure & GCP provider families with versions v0.37.0, v0.34.0 and v0.34.0, respectively, under xpkg.upbound.io/upbound-release-candidates.

[jeanduplessis]

@ulucinar could we move away from ssop naming in favor of the external naming of provider-family. It's more descriptive and should cause less confusion going foward.

[ulucinar]

@ulucinar could we move away from ssop naming in favor of the external naming of provider-family. It's more descriptive and should cause less confusion going foward.

Done. Renamed ssop binary's name as lint-provider-family.