Generally improve Automations user experience and code

[MichelleBlanchette]

Sadly, this will require a migration process so that Automation data is maintained between versions. It's certainly worth it to standardize and simplify the data storage and interfacing for Automations.

[MichelleBlanchette]

What is the goal of this? Could this instead be a problem with the database CRUD functions being excessively complex? Maybe the code could be simplified and some performance benchmarks should be recorded. Also, the frontend could maybe be changed to support a simpler backend architecture.

[MichelleBlanchette]

Note that there's several database queries executed on every page load related to retrieving Automations records. It's probably due to trying to hook them into the WordPress event system, but it still seems inefficient. Shouldn't you only need their hook name to register their behavior, and then just retrieve their full data when the hook actually executes? Additionally, the WordPress caching system can probably help further optimize this. I was certainly thinking of using it to optimize the main, Automations listing page.