Packet is now Equinix Metal

[displague]

The Packet branding should be updated to Equinix Metal.

Existing users should have more time to update their scripts from "packet" to "equinixmetal", so I propose adding a new Equinix Metal provider and deprecating the Packet provider. The options provided between the two providers will generally be common, but new features should only be introduced in the Equinix Metal provider.

Equinix Metal has an updated Terraform provider that was not a part of the hashicorp/ collection, the testing harness may require TF 0.13 to support this. This provider is mostly compatible with the Packet provider with the obvious renaming of resources (packet_* to metal_*). The Equinix Metal Terraform provider still honors the PACKET_AUTH_TOKEN environment variable, although METAL_AUTH_TOKEN is preferred. Existing Packet tokens continue to work in the EM API.

packngo is used between the Packet and Equinix Metal infrastructure, the API is mostly the same with the key difference being the API URL and some resource href attributes that refer to the updated base URL. API Tokens are common.

• Add Equinix Metal Provider
• Update Packet Provider branding
• Deprecate Packet Provider
• Extend Packet provider from Equinix Metal provider? (to avoid code and test duplication)
• Remove Packet Provider?

[displague]

A new Equinix Metal provider would benefit from new features not present in the Packet provider:

• Metro support (the Packet provider supports Facilities only)
• VLAN support (similar to support Linode VLANs #192)
• VRF support