[TASK] Turn on Usage portlet for existing evergreen deployments

[yolabingo]

Research Question

Our goal of enabling a Portlet diverges from the current Portlet management process in which Portlet changes handled exclusively by users in the backend after the initial install. Is there a mechanism to enable a Portlet after install without negative consequences such as reverting User's customization to the Portlet?

The goal is to enable the Usage portlet only once. If a customer moves or removes the portlet we should not restore or change the portlet on subsequent restarts. DotCMS may not support this functionality.

Acceptance Criteria

• [] Determine process to enable new Portlets on existing dotCMS with upgrade tasks
• [] Add Upgrade Tasks to dotCMS core to enable Usage portlet

[mboutillette-dotcms]

Confirmed with Todd that this has been completed - looked at a couple customer instances and Usage tool is in the System tool group.