Partial Pull Request for Issue #13357

Summary of Changes

Similar to #13524 this tries to make the JComponentHelper class resilient to cache related issues.

1. The database query is now fully stored and executed in a lambda function, this lambda function is passed to the cache controller instead of only instructing it to run JDatabaseDriver::loadObjectList()

2. Cache exceptions are caught and the lambda function will attempt to be run directly instead.

3. On a database failure, we're out of luck; sorry.

Testing Instructions

If the cache store fails to connect or the cache configuration is bad, the exceptions thrown by the cache API should be caught and JComponentHelper::load() try to manually execute the lambda function to load the data. The method currently catches all thrown RuntimeException objects but will now only catch JCacheException objects; in the case of a database error (all the database exceptions extend RuntimeException), we've got a bigger issue and this method shouldn't try to act as an error handler for that type of failure and let the application keep running.

Documentation Changes Required

N/A