Update bug and feature issues sections

Why is this change being made?

Examples

Team member recently got confused over the ~bug label on a couple of occasions:

Situation	Outcome	Link
Alert management list does not allow you to open an alert in the list in a new browser tab	Relabelled from bug to feature	gitlab-org/gitlab#225655 (closed)
		gitlab-org/gitlab#216799 (closed)
When there is too much data for productivity analytics to show performantly, the UI says There is no data available	Relabelled from bug to feature	gitlab-org/gitlab#217858 (closed)
Required approvals do not update on existing MRs when CODEOWNERS file changes	Deciding whether to relabel from bug to feature	gitlab-org/gitlab#11808
		gitlab-org/gitlab#224636

Impact

graph TD
  A[MVC is implemented] --> |Some of the feature in MVC is not what the user expected because of how we iterated| B(Issue with `bug` label is created and assigned SLO because of P/S labels)
  B --> C1(Perceived decrease in team quality because of increased bugs over time)
  B --> C2(Team are disincentivized to iterate because it feels like iteration leads to lots of bugs)
  B --> C3(A lot of time spent in the team discussing what is a bug vs a feature)	

Author Checklist

• Correct MR template applied (e.g blog post)
• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack