Updating language to reflect EBR CTA creation for Pr1 accounts only, process for non P1 and to remove mention of auto close of EBR as we are no longer doing so 2 months prior to renewal

Why is this change being made?

With the updates made to the process of EBR CTA creation to now be for PR1 accounts only, we needed to update the language in the handbook to reflect that. At the same time, removed note regarding the auto close of the EBR playbook 2 months prior to renewal, as this rule has been disabled.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (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 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 affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---