Update-compose-files

[dmunozv04]

Proposed changes

Updates docker compose files, removing obsolete tags like version and linting files so they are ordered alphabetically. Also adds an all in one docker compose example and a test for it.

Types of changes

What types of changes does your code introduce to the project: Put an x in the boxes that apply

• [x] Bugfix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I have read the CONTRIBUTING doc
• [x] I have signed the CLA
• [x] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

Further comments

This PR depends on #551 (without it docker tests won't run correctly on CI)