Bump compose version, remove dependency check

[wyarde]

Update example using latest Docker compose syntax (3.8).

Version 3 of Docker Compose got rid of the explicit dependency declaration; instead the applications should resolve dependencies themselves gracefully. From my tests, kibana will continue to try and eventually starts up just fine without the explicit dependency specified.

[mergify]

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b update_to_latest_compose <remote-repo>/update_to_latest_compose
git merge <remote-repo>/main
git push <remote-repo> update_to_latest_compose

[mergify]

This pull request does not have a backport label. Could you fix it @wyarde? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-/d./d is the label to automatically backport to the /d./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[mergify]

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b update_to_latest_compose <remote-repo>/update_to_latest_compose
git merge <remote-repo>/main
git push <remote-repo> update_to_latest_compose

[mergify]

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b update_to_latest_compose <remote-repo>/update_to_latest_compose
git merge <remote-repo>/main
git push <remote-repo> update_to_latest_compose

[mergify]

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b update_to_latest_compose <remote-repo>/update_to_latest_compose
git merge <remote-repo>/main
git push <remote-repo> update_to_latest_compose

[mergify]

This pull request is now in conflict. Could you fix it @wyarde? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b update_to_latest_compose <remote-repo>/update_to_latest_compose
git merge <remote-repo>/main
git push <remote-repo> update_to_latest_compose