W-8988823 Require Apex code coverage

[spelak-salesforce]

W-8988823

Requires each Apex class to have at least 95% code coverage.

Critical Changes

Changes

Issues Closed

New Metadata

Deleted Metadata

Definition of Done

Refer to Definition of Done to see any additional details for the items below:

• Any net new LWC work has JEST test coverage 50% or above
• Default Sa11y tests pass for all LWC components
• 🔒 Secure both Front-end (LWC) & back-end (Apex) as necessary
• 🔑 Grant users access in Permission Sets (Object, Field, Apex Class) as necessary
• Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name
• Make sure that ACs are updated (if any gaps)
• All acceptance criteria have been met
  • Developer
  • Code Reviewer
• Pull Request contains draft release notes
• Labels, help text, and customer facing messages are reviewed by Docs
• QE story level testing completed

[github-actions]

Hi 👋 @spelak-salesforce! Release Engineering asks that teams use the following process for routine reviews:

1. After creating a non-draft pull request that includes automation updates, a release engineer will be auto-assigned to the PR.
2. When dev review is complete and the PR is ready for the release engineer to review, add a "ready for RE review" label to the PR to let us know when the PR is ready for us to review.
3. If you've added the "ready for RE review" label but haven't received a review within a 36 hours, @-mention the assigned RE in a comment on the PR.
4. If you don't receive a response from the assigned RE by the end of the next business day (or your request is urgent), post a message to #sfdo-releng-support that includes a link to this PR and one of us will review as soon as we're able.

[github-actions]

This PR has been labeled as ready for Release Engineering review by
@spelak-salesforce. Reviews have been requested from: @davidmreed, @sella24.