When context uses component scan, parent class conditions are ignored in favor of nested class conditions.

[cagliostro92]

The solution is really simple and non-invasive: in the context scan flow, when scan(basePackages) is invoked, we deal with resources instead of classes. Before any further evaluations, these resources need to be sorted based on how many "$" are present in the filename. When a valid candidate is excluded because of a non-matching condition, the corresponding filename is added to a list. Before registering a candidate, this list is consulted. The candidate is registered if the list doesn't contain the candidate's parent filename.

Closes #29372

[jhoeller]

Closing this PR along with #29372 and #30750 since classpath scanning is meant to find such nested classes independently when they carry their own stereotype annotation.