Updated docker-compose.yml: replaced broken images with latest

[TAFKAMW]

The docker-compose.yml contained references to 3 images with version '4.1.0'. However, those images don't exist (anymore?).

Therefore I updated these 3 references to point to version 'latest'. At this moment this will effectively result in version '4.0.0' being downloaded.

Purpose

Resolves issues:
wso2/docs-apim#7405
https://github.com/wso2/samples-apim/issues/118

Goals

In stead of referencing a non-existent version of 3 images, this fix points to the 'latest' version of these images.

Approach

Replaced 3 entries of '4.1.0' in the docker-compose.yml to version 'latest'. At this moment this will effectively result in version '4.0.0' being downloaded

User stories

Enables https://apim.docs.wso2.com/en/latest/tutorials/scenarios/scenario-overview to works again.

Release note

Fixed broken image(-link)s.

Documentation

https://apim.docs.wso2.com/en/latest/tutorials/scenarios/scenario-overview

Training

https://apim.docs.wso2.com/en/latest/tutorials/scenarios/scenario-overview

Certification

N/A. The docker-compose was simply broken.

Marketing

N/A

Automation tests

N/A

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? no
• Ran FindSecurityBugs plugin and verified report? no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Samples

N/A

Related PRs

N/A

Migrations (if applicable)

Just clone latest version.

Test environment

N/A

Learning

https://github.com/wso2/samples-apim/issues/118#issuecomment-1779138182

[CLAassistant]

All committers have signed the CLA.

[YBriukhov]

I ran into the same situation described and after applying the suggested changes to docker-compose.yml I was able to move forward.
However, the next error (may or may not be related) was: "Error response from daemon: Conflict. The container name "/buildx_buildkit_default" is already in use by container "86c510e92e8c0c80faf8fdbbb97e974245b37aec4d30b6d205103e063b0d864b". You have to remove (or rename) that container to be able to reuse that name."
Full output here apim-tutorial.log

[YBriukhov]

I ran into the same situation described and after applying the suggested changes to docker-compose.yml I was able to move forward. However, the next error (may or may not be related) was: "Error response from daemon: Conflict. The container name "/buildx_buildkit_default" is already in use by container "86c510e92e8c0c80faf8fdbbb97e974245b37aec4d30b6d205103e063b0d864b". You have to remove (or rename) that container to be able to reuse that name." Full output here apim-tutorial.log

UPD: solved buildx_buildkit_default error by updating docker, which was installed by the snap using this command:
sudo snap refresh docker --channel=latest/edge