Moo is only used for an optional test:

MooseX-StrictConstructor-0.21 $ grep -Hnr '\<Moo\>'
t/no_build.t:6:use Test::Needs 'Moo';
t/no_build.t:18:    use Moo;
t/no_build.t:27:        'no errors when instantiating a Moo child of a strict superclass',
t/00-report-prereqs.dd:14:                                  'Moo' => '0',
t/00-report-prereqs.dd:64:                                 'Moo' => '0'
Changes:3:- The last release accidentally added Moo as a hard prereq when it's only
Changes:12:  BUILD subs (used internally by modules like Moo that have their own
META.json:29:            "Moo" : "0",
META.json:79:            "Moo" : "0"
META.json:956:                     "Moo"
META.yml:694:            - Moo
cpanfile:24:  suggests "Moo" => "0";
cpanfile:37:  requires "Moo" => "0";
dist.ini:12:module = Moo

https://pagure.io/releng/fedora-scm-requests/issue/25687

FEDORA-EPEL-2020-4794fda156 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4794fda156

perl-MooseX-StrictConstructor-0.21-11.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4794fda156

FEDORA-EPEL-2020-4794fda156 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.