Error applying Project Config when it contains a new Single Section and SEOmatic is installed

Describe the bug

Applying project-config changes that contain a new Single section will error saying the section (that you are creating) has no entry type when SEOmatic plugin is installed.

SEOmatic does not appear in the stack trace of the error. SEOmatic does appear in the web.log and console.log but it looks like only for it’s Loaded Event. However whilst trying to debug this issue our team disabled each of the 10+ plugins on the site we are building and only disabling SEOmatic allowed us to apply the project config containing a new Single successfully, and it is reproducible on a fresh craft install with only SEOmatic added.

To reproduce

Steps to reproduce the behaviour:

1. Install Craft Pro Trial
2. Install SEOmatic Trial
3. Export the DB
4. Create a new Single section.
5. Import the exported DB
6. Touch project config
7. Apply project config

Expected behaviour

Project config should apply without error and add your new Single section.

Screenshots

Versions

• SEOmatic Plugin version: 3.4.23
• Craft version: 3.7.30.1
• PHP version: 7.4.25
• MySQL version: 5.7.23
• Laravel Valet 2.16.1

project-config-console.log
project-config-web.log
project-config-error.txt

Start by reproducing the project-config apply failure with Craft Pro Trial and SEOmatic Trial, then compare the attached project-config-console.log, project-config-web.log, and project-config-error.txt. Trace the project-config import path involved in creating a new Single section and identify why SEOmatic causes the missing-entry-type error. Done means the project config applies successfully with SEOmatic installed.