ci(issues): update issue template

[ReenigneArcher]

Description

Update issue template.

Screenshot

Issues Fixed or Closed

Type of Change

• 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)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.97%. Comparing base (ccd6559) to head (a19f589).
Report is 144 commits behind head on master.

Additional details and impacted files

@@          Coverage Diff           @@
##           master   #2277   +/-   ##
======================================
  Coverage    8.97%   8.97%           
======================================
  Files          94      94           
  Lines       17389   17389           
  Branches     8267    8267           
======================================
  Hits         1560    1560           
  Misses      12963   12963           
  Partials     2866    2866           

Flag	Coverage Δ
Linux	6.79% <ø> (ø)
Windows	4.16% <ø> (ø)
macOS-12	10.04% <ø> (ø)
macOS-13	9.96% <ø> (+0.01%)	⬆️
macOS-14	10.25% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.