Add row on rejecting in application review

Why is this change being made?

The table that outlines the expectations on the TA team around rejecting candidates isn't clear on whether we need to reject folks at application review.

I'm of the opinion that all candidates who apply should be informed when they're rejected as it's the right thing to do, it aligns with the handbook guidance of "The candidate should always be notified if they've been rejected.", and it's better for our employer brand. This MR adds a line on rejecting folks at application review and removes the same table in the "interviewing" page so there's a single source of truth.

I wanted to open this up after this Slack discussion

@Kellymurdock - please may you review this change?

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)