perf(autoloader): Force own autoloader

[ChristophWurst]

And don't register any generic PSR-4 nor PSR-0 loader in server.

https://github.com/nextcloud/server/blob/473c546b5c562e19ba8f9d3aef9cd64d2458cda7/lib/private/legacy/OC_App.php#L284-L290

Benchmarks

Blackfire comparison graph on IO wait

Blackfire recommendations before

Blackfire recommendations after

🖼️ Screenshots

🏚️ Before	🏡 After
🦥	🐌

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included
• 📘 API documentation in docs/ has been updated or is not required
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required
• 🔖 Capability is added or not needed

[ChristophWurst]

metrics.composer.autoload.find_file.count 117 <= 50

Server and this app have authorative autoloaders. But I think the generic autoloader in server tries to load this app's files before the shipped autoloader gets a change. If the generic autoloader isn't registered the shipped autoloader gets a chance to load the file.

[nickvergessen]

Thanks, I was always tempted to add one, but I disliked the "ah forgot to run bash build/autoload..." from server. I didn't know it's possible to do it for 3rdparty but not the own classes :)

[nickvergessen]

Seems CI doesn't like it

[ChristophWurst]

that means composer i didn't happen

[nickvergessen]

that means composer i didn't happen

Right, it was run only after the app was enabled.
Fixed now

[ChristophWurst]

Tip: nextcloud/mail#8020 to relax the autoloader on dev setups and make it find new files too