Improve update/upgrade logic for plugins in TN Core
Description
From user perspective, it doesn't make sense to have update/upgrade as different things for a plugin as user is not managing the internals of how the plugin is working and hence we should automatically improve the process/workflow where we intelligently apply an upgrade if one is applicable or an update if upgrade is not applicable for a plugin ensuring from user perspective it's just a single operation which is getting the newer version of the plugin.
From user perspective, it doesn't make sense to have update/upgrade as different things for a plugin as user is not managing the internals of how the plugin is working and hence we should automatically improve the process/workflow where we intelligently apply an upgrade if one is applicable or an update if upgrade is not applicable for a plugin ensuring from user perspective it's just a single operation which is getting the newer version of the plugin.