Ensure Generated "Other Community Standards" Are Relevant to Project

[Alexhuszagh]

In a similar fashion to #7, the current default-generated Code of Conduct includes community standards for both Github and NPM, by default, even if the project does not use Github, nor NPM.

Sample Output

### Other Community Standards

As a project on GitHub, this project is additionally covered by the [GitHub Community Guidelines](https://help.github.com/articles/github-community-guidelines/).

Additionally, as a project hosted on npm, it is covered by [npm, Inc's Code of Conduct](https://www.npmjs.com/policies/conduct).

Enforcement of those guidelines after violations overlapping with the above are the responsibility of the entities, and enforcement may happen in any or all of the services/communities.

This produces less-than-stellar defaults for projects, say, hosted on other hosting services, or using other programming languages.

Hosting Service Fix
1). Read the output of git remote -v.
2). Parse the output depending on SSH or HTTPS origins, and find the host domain name.
3). Determine if the repository is hosted on Github, Gitlab, Bitbucket, or other.
4). Add the relevant CoCs or community standards in a relevant fashion.

Package Manager Fix
1). Determine if there's a package.json without the "publish": false option.
2). Determine if there's a Cargo.toml without the publish = false option.
3). Maybe whitelist additional programming languages, like Python, etc.