Thanks to @jdgri for assisting with API tests to confirm support

Thanks to @pwaring for assisting with API tests to confirm support,
and reaching out to Mythic Beasts to obtain a fix

Thanks to @actazen for assisting with API tests to confirm support

Thanks to @yzguy for assisting with API tests to confirm support

Thanks to @yzguy for assisting with API tests to confirm support

* Removed conversion of DYN records to A records
* Updated test fixtures to change test DYN to an A record

* Removed conversion of URL and STEALTH records to CNAME records
* Updated test fixtures to remove URL conversion testing

This provider class for easydns.com adds support for basic dns records
through the easyDNS v3 API.  Support for dynamic and geo based dns
records is planned for a future update.

Sample configuration for the easyDNS provider are:

  easydns:
     class: octodns.provider.easydns.EasyDNSProvider
     token: <token>
     apikey: <key>

The token and key values are found on the easyDNS customer portal at:

https://cp.easydns.com/manage/security/api/production_info.php

Also, below are some optional configuration parameters which can be
added to override the class defaults.  By default the provider class
connects with the LIVE easyDNS API, if you wish to perform testing
with the easyDNS Sandbox API you can enable it by adding the following
configuration parameter:

     sandbox: True

Note, the API token and key are different for the sandbox than they
are for the production API, you can obtain sandbox credentials at:

https://cp.easydns.com/manage/security/api/sandbox_info.php

Lastly, if you have created Domain Portfolios through the easyDNS CP
you can configure which portfolio new domains will be added to by
supplying the portfolio option with the name of your portfolio.

     portfolio: <portfolio name>

- added unit tests for apply functions
- added another json config file for this
- 100% code coverage reached

- added test cases for test_apply, testing for basic create, update, delete records
- added previous state json file in test/fixtures to do the above

- added test cases for testin populate()
- added mock request responses in tests/fixtures/
- updated requirements.txt to require edgegrid-python

`Included` and `Excluded` can be used to filter records for one or more specific provider(s). This can be extremely useful when certain record types are not supported by a provider and you want only that provider to receive an alternative record.

See also: https://github.com/github/octodns/issues/26