@W-14204419 - Update RD2 preflight class_path to work-around installer errors

[force2b]

A recent change to CumulusCI resulted in a regression for certain custom tasks. Before this commit:

$ cci task run is_rd2_enabled
Error: module 'tasks' has no attribute 'is_rd2_enabled'

Run this command for more information about debugging errors: cci error --help

This resulted in an error when running preflight checks for the enhanced-recurring-donations plan in MetaDeploy. After:

$ cci task run is_rd2_enabled
is_rd2_enabled

  Description: This preflight check ensures that Enhanced Recurring Donations is enabled

  Class: tasks.check_rd2_enablement.is_rd2_enabled
[...]

Critical Changes

Changes

Issues Closed

Community Ideas Delivered

Features Intended for Future Release

Features for Elevate Customers

New Metadata

Deleted Metadata

[github-actions]

Hi 👋 @force2b! 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.