Add issue template and pull_request template [issue #113]

[Corsair-cxs]

Achive #113
What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe: Add issue template and pull_request template

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch for ros_openvino_toolkit (or to a previous version branch), not the master branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• All tests are passing: https://github.com/intel/ros_openvino_toolkit/blob/dev-ov2020.3/.github/CONTRIBUTING.md#development-setup
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Reference

https://github.com/vuejs/vue/blob/dev/.github/COMMIT_CONVENTION.md

[LewisLiuPub]

good template.
But before merging, I need to have a line-to-line review with you. we need suitable steps and templates, try to make them simple and clear, rather than too complex.

[LewisLiuPub]

sounds like it is not good to store such .md files under folder .github/?

[LewisLiuPub]

I will arrange a review meeting with you, you needn't do anything about its updating before the meeting. @Corsair-cxs.

Thanks.

[Corsair-cxs]

I will arrange a review meeting with you, you needn't do anything about its updating before the meeting. @Corsair-cxs.

Thanks.

OK!

[LewisLiuPub]

we'll merge this PR first and say any updates to be needed.