bug #57275 Fix autoload configs to avoid warnings when building optimized autoloaders (Seldaek)

This PR was merged into the 5.4 branch.

Discussion
----------

Fix autoload configs to avoid warnings when building optimized autoloaders

| Q             | A
| ------------- | ---
| Branch?       | 5.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead -->
| License       | MIT

The next composer release next week (you can try `composer dump -o` with snapshots right now) warns a bit more about classes which do not match the psr-4 rules they are found in.. Symfony has quite a few false positives there because the rules are using `""` as path for all individual components so all files of the component are scanned by default. I already made sure Composer excludes the vendor dir by default now, and this fixes the rest of the errors I noticed.

Commits
-------

8882804add Fix autoload configs to avoid warnings when building optimized autoloaders

Author: fabpot

composer.json

@@ -34,7 +34,8 @@
         "files": [ "bootstrap.php" ],
         "psr-4": { "Symfony\\Bridge\\PhpUnit\\": "" },
         "exclude-from-classmap": [
-            "/Tests/"
+            "/Tests/",
+            "/bin/"
         ]
     },
     "bin": [