Add support for GitHub Enterprise for github_deploy_key

[dcode]

SUMMARY

I use GitHub Enterprise and would like to use the Ansible modules to manage deploy keys and such. The API is generally the same for public GitHub, it's just a URL change.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

github_deploy_key

ANSIBLE VERSION

ansible 2.5.3
  config file = None
  configured module search path = [u'/Users/username/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/username/.pyenv/versions/2.7/envs/ansible/lib/python2.7/site-packages/ansible
  executable location = /Users/username/.pyenv/versions/ansible/bin/ansible
  python version = 2.7 (r27:82500, Oct 10 2017, 09:33:49) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]

ADDITIONAL INFORMATION

Admittedly, I made these changes a few months ago and don't remember all the ins and outs. I think some of the edits I made because pylint was giving lots of complaints in Atom. I'm willing to go back and forth, but I think this is an important feature to have on all the GitHub modules.

[ansibot]

@dcode this PR contains the following merge commits:

• 277d001

Please rebase your branch to remove these commits.

click here for bot help

[ansibot]

The test ansible-test sanity --test validate-modules [explain] failed with 1 error:

lib/ansible/modules/source_control/github_deploy_key.py:0:0: E309 version_added for new option (api_url) should be 2.6. Currently 0.0

click here for bot help

[webknjaz]

N.B. this PR's fork repository or branch has been deleted by the owner.
If anyone is up to pick up the work they can pull the branch using this guide https://help.github.com/articles/checking-out-pull-requests-locally/#modifying-an-inactive-pull-request-locally and then re-submit the fixed branch as a new PR.
If the author is going to do it themselves, they'll need to make sure to restore the fork and the branch within with the same name.

[ansibot]

@dcode Your branch does not contain a shippable.yml file. Please rebase your branch to trigger running of current tests.

click here for bot help

[gundalow]

@dcode This looks useful, if you could please update DOCUMENTATION as I've put above, we can get this merged. Thank in advance.

[gundalow]

@dcode
Thank you for your PR.
As part of reviewing the backlog of PRs we are looking at PRs older PRs that haven't been updated in a while

Given that:

• PR has failed CI May 2018
• This is a feature rather than a bug fix
• The source branch (in your fork) no longer exists

Therefore I'm going to close this.

If you or anyone else wants to continue with this work then please do feel free to create a fresh PR and @mention the previous reviewers in here.