Remove Cannot() records for Azure and R53 ALIAS records

[j-f1]

It was confusing to me that most services had a “-” in the table for R53_ALIAS and AZURE_ALIAS while some had an “X.” I’ve removed the Cannot() calls for the corresponding capabilities from the providers that had them since it will never make sense for another provider to support these record types.

[j-f1]

Now that I think about this a bit more, would it make sense to entirely get rid of the rows for those record types? They really are only applicable to the one provider and people could find out that they’re supported by browsing the pages for each provider separately. R53 and Azure could also be updated to show support for the ALIAS record type with a tooltip indicating you have to use the custom one.

Relatedly, should support for the URL type be added as a row? It looks like more providers than Namecheap support it.

[tlimoncelli]

I agree that R53_ALIAS and AZURE_ALIAS make the chart look ugly. However they should be listed somewhere. Maybe a bullet list of provider-specific types?

As far as URL... different providers implement that kind of thing differently. We probably should have called that NAMECHEAP_URL. My preference is to have GENERIC_REDIRECT() that supports a lowest-common-denominator redirect that "does the right thing" for each provider. (maybe flags for 301 vs 301 redirects but nothing else).