Create performance specific endpoint

[circlecube]

We should have endpoints for performance data in this module so that it can manage performance values independently of the plugin settings apis.

This involves migrating the CachingController.php into this module. Then we can have the js components directly calling the endpoints for the performance module and remove it from plugins.

• https://github.com/bluehost/bluehost-wordpress-plugin/blob/main/inc/RestApi/CachingController.php
• https://github.com/newfold-labs/wp-plugin-hostgator/blob/main/inc/RestApi/CachingController.php

We should also create an endpoint for cacheLevel getting/setting. Similar to how the settings are managed in the plugins:

• https://github.com/bluehost/bluehost-wordpress-plugin/blob/main/inc/RestApi/SettingsController.php#L124-L125

These can live at a new API namespace newfold-performance/v1/

We should use (or set up) a PHP filter for the data injected into the data store for the app. We can hook into that in the module and add the cacheLevel value to the data store for consumption in the app. This way we don't have to load it independently in the module and the app can be aware of it.

At a high level, it will be good to establish a pattern where modules manage their own data but also expose it to be shared by the plugin store (Likewise, the coming soon boolean should live in that module). The data can be loaded in the runtime or container or hook, but the module itself should house the business logic that manages the data. It can also expose helper methods for the plugin or other modules to access.