docs: record cloud-specific quirks

[lucab]

Cloud providers may have specific quirks and restrictions which could result in surprising behaviors of coreos-metadata or which could require workarounds in the codebase. Those should be documented in the repository, so that we have an explicit note to reference.

The first example of this has been reported at coreos/bugs#2468 (comment).
Azure may (or may not, depending on agent version and settings) prevent non-root users to reach the metadata endpoint for security reasons. This affects how the coreos-metadata service can be run.

[lucab]

Additional cloud-specific quirk for OpenStack, coming from openshift/machine-config-operator#964 (comment).

As Openstack is not an homogeneous platform and the metadata component is only optional, the static Ignition platform ID is not useful there (i.e. it can't signal whether the metadata endpoint exists or not).
Thus, there is a more specific openstack-metadata provider ID for that, which is usually not baked into images kernel arguments (but can be opted-in manually).
For the same reason, [email protected] does not automatically work on OpenStack, but requires a custom drop-in setting ${AFTERBURN_OPT_PROVIDER} and ConditionKernelCommandLine.

[prestist]

This falls into a similar situation => #138

[bgilbert]

The OpenStack one is no longer relevant since #462, though CloudStack has similar behavior (#856).