Investigate if using Squash is viable for unifying compression APIs

Whilst the balance is leaning towards implementing the project using MariaDB services, the Squash approach is still on the table. We need a bit more information before we can weigh accurately how much work and maintenance may go into the services approach and how much convincing work we might need to do if we pick Squash.

In any of these cases, this research will turn out to be super helpful for the coding part of the project, so here are the items we need to follow:

1. Get the list of all Storage Engines that use compression libraries
2. Get the list of all compression libraries used by storage engines supported by MariaDB
3. Investigate if Squash supports all the APIs used by storage engines. Whilst we are still in the search mode within these code places, get the functions names of the compression libraries where Storage Engines make API calls and compile a list with them.

We also have consider mariabackup and galera sst to the above