Improved the pull request and added more issues templates. Fixes #47

[Gbahdeyboh]

What this PR does / why we need it:
This pull request fixes the issues addressed in issue #47

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #47 #52 #50

Special notes for your reviewer:

The Pull Request template was improved and the Issue templates were re-organized.

Issue Templates

There are now multiple issue templates that can be found in the .github/ISSUE_TEMPLATE folder.
This way, when contributors want to create a new issue, they will be faced with options to select a template as shown below;

The above shows an option to select one issue template, but in our case, contributors will be faced with three templates that have descriptions that help them decide which is best for their issues.

Why do we need to split issue templates?

There are different reasons why a contributor might want to create an issue. These templates make it quite easy for them to get started. However, one single template cannot suit the needs of all contributions as their intents and contributions would always be different. This is why I created a broader scope of sections for these templates.

There are 3 major things a contributor to any open-source documentation repository issues often want to do, and they are;

• Suggest the creation of entirely new documents
• Suggests improvements or report errors on already existing documentation.
• Report bugs, and make a feature request to the tech used to develop the documentation.

The templates created covers this broad spectrum of issues and would help contributors do the following;

• It helps contributors quickly decide the category of their issue.
• It gives them precise questions in each category
• It makes it more easier for them to file issues when all they have to do is to answer a set of pre-defined questions regardless of what type of issue they have.
• They have the option to create an issue with nit template if none of the issues meet their needs.

Checklist:

• Fixes #
• Signed the commit for DCO to be passed
• Labelled this PR & related issue with documentation tag

Update

I added commits that adds more context to different installation modes.