Plugins are being recompiled when not needed under some circumstances, resulting in slow Logon

When an application other than Jiwa.exe invokes the Logon method of JiwaApplication (e.g.: 3rd party applications, REST api, plugin scheduler) the plugins are often recompiled because the compilation path and assembly locations of plugins differs to what is expected.

The CompanyName, ProductName and the Version of the Application referencing JiwaApplication make up part of the path used for plugin compilation - This can cause plugins to be always unnecessarily compiled when the Logon method is invoked.

We should use a static CompanyName of "Jiwa Financials", a static ProductName of "Jiwa 7" and use the version of the JiwaApplication assembly instead of the Application version when building the path to determine where plugins are compiled to or loaded from, and also in the custom AssemblyResolve handler when attempting to locate assemblies referenced by a plugin.