Do not analyze excluded files

[j6s]

resolves #156

I noticed, that FileFinder::findSrcFiles has an $excluded parameter, that is never specified - but I didn't want to do too many changes in this PR.

[j6s]

Discussion: As far as I can see, this means that the exclusion from configuration in StatementBuilder::selectOrigins can be removed because they are not part of the set in the first place, right?

[carlosas]

Yes, this was done in this way thinking that excluded files would not be part of the origin set, but they would be for the destination set. Meaning that ExcludedFile would not be checked for rule violations but would be checked as a relation for other classes.
On a later version, I made the rules recognize relations for classnames that are not in the map, so the only benefit of still having the excluded files in the map would be looking for them with inderect selectors (like classes that implement xyz). Anyway the memory consumption of this decision could be heavy in some code structures (like your case), so I think the benefit of having "hard exclusion" is higher 👍

I'm already thinking on a secondary traverser (only for classnames/parents/interfaces) to be able to indirectly detect these excluded files (or even vendors), but this will probably come in a future major version.