docs(readme): add Greek translation and update language navigation

[pirrozani]

Issue for this PR

Closes #15279

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

I have added a Greek translation README.gr.md file for Greek speaking users for better understanding.

How did you verify your code works?

I have tested locally.

Screenshots / recordings

No UI change

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

If you do not follow this template your PR will be automatically rejected.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Potential Duplicate Found

PR #15277 - "Add Greek translation (README.gr.md) and language link to main README"

• Add Greek translation (README.gr.md) and language link to main README #15277

Why they're related: Both PRs add a Greek translation file (README.gr.md) and update language navigation in the main README. This appears to be a duplicate or very closely related PR addressing the same feature. PR #15277 was likely submitted before PR #15281 and should be reviewed first.

[andreas-agouridis]

@pirrozani This PR contains exactly the same work as my PR #15277 which I submitted earlier.

My PR was submitted first and is waiting for approval. Please check the timestamps @anomalyco/maintainers for verification.

Copying someone else's work and creating a new PR violates the contribution guidelines of Open Source.

[pirrozani]

Hi everyone,

I noticed that another PR was submitted around the same time addressing this same logic.

Just for clarity on the workflow: I checked for existing issues before starting but i found none, so i created #15279 to document the docs feature as per the Contributing Guidelines. I then opened this PR to resolve that specific issue.

It seems we both had the same idea at the very same time! I'm happy to collaborate or let the maintainers decide which implementation fits the codebase best. I just wanted to ensure the process stayed aligned with the project's documentation.

Regardless of which PR is moved forward, I'm just glad to see this being resolved. Cheers!