Adding new issue template

[zendranm]

 know more

Solves issue #1204

Describe your change:

• [ ] Add an algorithm?
• [ ] Fix a bug or typo in an existing algorithm?
• [x] Documentation change?

Checklist:

• [x] I have read CONTRIBUTING.md.
• [x] This pull request is all my own work -- I have not plagiarized.
• [x] I know that pull requests will not be merged if they fail the automated tests.
• [ ] This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
• [ ] All new JavaScript files are placed inside an existing directory.
• [ ] All filenames should use the UpperCamelCase (PascalCase) style. There should be no spaces in filenames. Example:UserProfile.js is allowed but userprofile.js,Userprofile.js,user-Profile.js,userProfile.js are not
• [ ] All new algorithms have a URL in its comments that points to Wikipedia or other similar explanation.
• [ ] If this pull request resolves one or more open issues then the commit message contains Fixes: #{$ISSUE_NO}.

[Panquesito7]

The feature request template is not really applicable...

I still think we should keep the feature request template. For example: what if I want to add a new workflow or functionality and make an issue before making any PRs? @raklaptudirm, what do you think about this?

[raklaptudirm]

The feature request template is not really applicable...

I still think we should keep the feature request template. For example: what if I want to add a new workflow or functionality and make an issue before making any PRs?

@raklaptudirm, what do you think about this?

We should explicitly mention in the issue template that it is not for requesting algorithms imo.

[zendranm]

@Panquesito7 @appgurueu Since there is not much time until the end of the Hactoberfest, would you mind adding the hacktoberfest-accepted label to this PR? I will add any required code-review changes once I get a response here.