chore: add readme

[JaeAeich]

This PR is for README.

This PR was branched on top of last PR #95 which had some changes:

• Pinned pip version because CI failed on resolving python deps and asked for a specific pip version range.
• docker-compose has been depricated and docker compose comes as plugin ever since v3.
• Added some type hints to resolve mypy errors.

Summary by Sourcery

Documentation:

• Add a README file with information about the project, installation instructions, contribution guidelines, and contact information.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds initial documentation for the proWES project, including a README, contribution guidelines, and basic project information. It also updates the CI to pin the pip version.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Added a comprehensive README file with details on proWES, including its purpose, features, and usage instructions.	Added a synopsis section. Added a description section. Added installation instructions. Added contribution guidelines. Added versioning information. Added license information. Added contact information. Included badges for license, chat, and CI. Added logos for GA4GH, ELIXIR, and ELIXIR Cloud & AAI.	README.md
Updated CI to pin pip version.	Pinned pip version to 24.0.x.	.github/workflows/main.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @JaeAeich - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[JaeAeich]

@uniqueg Please ignore the commits from the previous PR, this PR is on top of it so the CI don't fail.

[uniqueg]

Maybe amend the description to say why you pinned the Pip version. Also, you could mention that you added a type hint (presumably because Mypy complained), updated the Docker Compose call (as required by recent versions) and restricted the FOCA version.

[JaeAeich]

@sourcery-ai review

[sourcery-ai]

Hey @JaeAeich - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[JaeAeich]

Maybe amend the description to say why you pinned the Pip version. Also, you could mention that you added a type hint (presumably because Mypy complained), updated the Docker Compose call (as required by recent versions) and restricted the FOCA version.

Those were for the last PR (those files aren't here anymore) but still added them here too.

[uniqueg]

Fixed a type, now LGTM :)