This will make easier to make sure the service is running when the
development container is started.
Before after the first time the container was created, if it was
restarted you needed to run the boot.sh script manually to start the
service.
Previously, executing Active Record tests against the trilogy adapter
within a devcontainer would fail with the error message:
```
Trilogy::SyscallError::ENOENT: No such file or directory - trilogy_connect
- unable to connect to /tmp/mysql.sock (ActiveRecord::StatementInvalid)
```
