Including inside a component results in yaml errors

Summary

Starting in GitLab 18.6, when referencing a component that incorporates its own dependencies via a wildcard reference an error is encountered in the CI - unknown keys in 'extends' (.[component_name]).

Updating the component to directly reference each included file instead of using a wildcard resolves the error.

Steps to reproduce

1. Create a component in your namespace.
2. Use include to incorporate additional yaml files in the component with a wildcard * or ** to include multiple files or directories.
3. Run a pipeline that includes this component and see the error in question.

Example Project

Internal GitLab.com link. I'll be adding it to a comment below.

What is the current bug behavior?

Error unknown keys in 'extends' (.[component_name]) will be occurred when including a compenent that has its own includes referenced via wildcard. Error is resolved when included files are individually referenced in the yaml instead of using a wildcard.

What is the expected correct behavior?

Included files will be added with no errors.

Relevant logs and/or screenshots

This merge request from 18.6 updated wild card rules to prevent situations where files could include themselves unintentionally: !211424 (merged)

This may have caused or be related to this change in behavior.

Output of checks

This bug happens on GitLab.com