[5.3] Optimize load of smart search plugins language

[Denitz]

Summary of Changes

Currently, \Joomla\Component\Finder\Administrator\Helper\LanguageHelper::loadPluginLanguage() uses a database query to get list of available finder plugins and next loads their language files.

This database query is useless because we can use native PluginHelper::getPlugin('finder') method which provides additional benefit (no extra database query is executed).

Additionally, the language load should be performed using system-wide $extension key like plg_finder_content to prevent duplicate language file load.

This method is called in all com_finder views plus mod_finder display, we can remove extra database and prevent duplicate language load.

Testing Instructions

Apply patch. Test smart search views in frontend, check smart search module display.

Actual result BEFORE applying this Pull Request

See extra database query like

SELECT `name`,`element`
FROM `jos_extensions`
WHERE `type` = 'plugin' AND `folder` = 'finder' AND `enabled` = 1

Expected result AFTER applying this Pull Request

All views and module work as usual, no extra database query

Link to documentations

• No documentation changes for docs.joomla.org needed
• No documentation changes for manual.joomla.org needed