Might be possible/make sense to allow it to be configured later, but for now
Route53 doesn't support it so we'll go with 1 to make sure that things match
up behavior-wise.

Normalize MX exchange to lower-case, fix #322

AzureProvider: update for azure-mgmt-dns 2.1.0 and add support for CAA records.

Route53Provider dynamic record support

Note that you can't specify a Host header for these which I believe will
complicate the ability to use this. Figuring that out will have to wait
until I or someone else has a use case for these...

This will ensure that deletes come before creates which are before upserts and
that records that uses aliases always come after their target (though implicitly
based on sorting types and not explicitly by looking at them.)

DynProvider only SUPPORTS_DYNAMIC if traffic_directors_enabled

add supports check to DNSMadeEasy Provider

CloudflareProvider: unpack long SRV records correctly

Add healthcheck option 'measure_latency' for Route53 provider

Route53 allows to monitor latency information on the dashboard
and using CloudWatch. While that is a nice to have function,
it is not necessary for a DNS failover scenario and increases
Route 53 costs.
To maintain backward compatibility, the default for this option
when ommited is true.

Dynamic records dyn

Make SUPPORTS_DYNAMIC an optional property, defaulting to False

Co-Authored-By: ross <ross@github.com>

Co-Authored-By: ross <ross@github.com>

Version bump to 0.9.4 & CHANGELOG.md update

Adding more details to OctoDNS docs