Issue and PR Template

[T-Crypt]

@prasanthrangan

I think we should work on a tempalate for Pull Requests and issues.

Something like:

PR Template

<!--- Provide a general summary of your changes in the Title above -->

## Description
<!--- Describe your changes in detail -->

## Related Issue
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] This change requires a documentation update

## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

Issue Template

### Prerequisites

* [ ] Can you reproduce the problem?
* [ ] Did you google this to see if it is a common arch linux problem?
* [ ] Are you running the latest version?
* [ ] Did you check the FAQs on the Wiki?
* [ ] Did you perform a repository search for related issue?

### Description

[Description of the bug or feature]

### Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [and so on...]

**Expected behavior:** [What you expected to happen]

**Actual behavior:** [What actually happened]

### Versions

You can get this information from executing `Yay -Qs (packagename)` or `Pacman -Qs (packagename)`

[T-Crypt]

@prasanthrangan, I just need your help with this cause the old way of doing this with a .github/issue_template.md is depreciated and it now relies on the settings on the repository.

Issue Template

[prasanthrangan]

thank you so much bro... the templates looks good to me!
Looks like I've to create these templates in repo settings, I'll look into it..