feat(issues): new format for issue templates

[NGL321]

Merged the issue templates into a single template in order to simplify triage, reduce miscategorization and duplicates, and reduce work to submit while still requiring sufficient information.

Provides opportunities to add reproduction-steps for bugs, desired behavior for feature-requests, and guides support questions to Stack Overflow without disallowing the cross-post here.

Looking for feedback.

---

Pull Request Checklist

• Testing
  • Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
  • CLI change?: coordinate update of integration tests with team
  • cdk-init template change?: coordinated update of integration tests with team
• Docs
  • jsdocs: All public APIs documented
  • README: README and/or documentation topic updated
  • Design: For significant features, design document added to design folder
• Title and Description
  • Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
  • Title: use lower-case and doesn't end with a period
  • Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
  • Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"
• Sensitive Modules (requires 2 PR approvers)
  • IAM Policy Document (in @aws-cdk/aws-iam)
  • EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
  • Grant APIs (only if not based on official documentation with a reference)

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

[eladb]

Looks great

[eladb]

Worth separating CDK CLI (“cdk --version”) version and modules version

[eladb]

@NGL321 make sure that the new template will automatically add the needs-triage tag to new issues. There's a way to do that, not sure exactly how...