Too many LORAs on host machine breaks connection in A1111

[As4shi]

Describe the bug
When having a large amount of LORAs on the host machine (the one hosting the A1111 instance), it might be impossible to connect through the app.
This seems to happen because it takes the API (sdapi/v1/loras) a long time to gather all the data and respond.

I have roughly 2500 LORAs atm, and I confirmed that starting A1111 without any LORAs made it possible to connect through the APP. (yes, I know, that is a lot and all that, but better have what you need when you need it, right?)

I'd like to also clarify that, perhaps surprisingly, the regular WebUI functions normally and I don't see any relevant performance issues on it.

To Reproduce
Steps to reproduce the behavior:

1. Download a large amount of LORAs
2. Start/Restart the A1111 instance
3. Try to connect through the APP
4. It won't connect due to the API not responding in time

Expected behavior
The app should have waited more and connected normally, or simply given up on acquiring the LORAs information, and then given a warning to the user about it.
Or maybe run this specific request async and then update the LORA list later, not sure how viable that is tho.

Alternatively, as a hotfix that is less intrusive than needing to rename a folder every time I want to use the APP, perhaps an option to disable the LORA feature on the app would be enough.

Screenshots
I don't see the need for screenshots, but let me know if you need something in specific.

Desktop:

• OS: Win10