Auto-update MindsDB Container When New Image is Released

[MinuraPunchihewa]

At the moment, since the extension is using Docker Compose to bring up the containers, if the MindsDB image (mindsdb/mindsdb:latest) has already been pulled by the user (or if the extension was installed) and a new version of the image is released subsequently, the extension will continue to use the old version of the image. This is the default behavior of Docker Compose.

Ideally, each time a new version of the MindsDB image (latest tag) is released, the extension should begin using it. However, one slight issue that arises in doing so is the fact that, because Docker Compose will spin up a brand new container with the new version of the image that is pulled, any changes that were made to the previous container will be lost. This applies mostly to the dependencies that are installed for integrations by the user; these will be lost as a result of the update.

Therefore, while the image is auto-updated, it is also necessary to persist the dependencies that were installed by the user across new versions.

[MinuraPunchihewa]

Only partially resolved by #12