Clarify weighting and labeling for CI planning breakdown

Why is this change being made?

As part of the CI monthly retrospective we identified that an effort involved with an issue when a feature flag is involved is not reflected in the weight.

Also, an issue should be labeled as bug, feature, performance, etc. according to the job to be done as per proposal. An issue may start as a bug but we end up introducing a new feature instead. Then the issue should reflect that so that a release post is created.

Author Checklist

• 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 one of the people listed in the "Maintained by" section in on the page being edited.
  • 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. (this requirement has been removed pending identification of a new DRI for the handbook)