1. Update `plugin_actions` to support translating the `name` field using language from the plugin. The plugin can then set an action that will represent the language definition to use (e.g. "SupportManagerPlugin.nav_primary_client.main")
2. Whenever plugin actions are retrieved, load up and instantiate the associated plugin
   • Call $this->_(..plugin definition..) on the plugin action definition to translate it

• The navigation cache may need to be reset whenever someone changes their language or a plugin is installed/upgraded (which may or may not already take place)

Note: The language for the actions are assumed to come from /plugins/plugin_name/language/en_us/plugin_name_plugin.php. If not set here then it will use the name of the plugin as given

When a plugin (e.g. Support Manger) is installed, it can register navigation links. Currently, these navigation links are translated definitions of the current language. Since these definitions are saved in the database, they are not translated into the admin/client's language.

e.g. An admin can install the Support Manager plugin (default lang = en_us). If a client uses a different default language, they will always see the en_us version of the translation for the Support Manager navigation links.

We may want to consider saving the navigation definition term rather than it's definition translation, and allow for the navigation to load up the plugin's language file(s) to translate the definition on the fly to better support multi-language navigation links.