Update Atlas configuration

[MaximilianAnzinger]

This pull request introduces configuration changes to enable the Atlas service and add initial AtlasML settings across several environment variable files. The main focus is on preparing the environments for Atlas integration, with AtlasML disabled by default but configurable for testing purposes.

Atlas and AtlasML configuration updates:

• Enabled the atlas service and added an atlasml section (with enabled: false) in group_vars/artemis_prod_like_common.yml to standardize Atlas configuration across production-like environments.
• Enabled the atlas service and added an atlasml section (with enabled: false, plus base-url and auth-token for AtlasML) in group_vars/artemistest3.yml to support Atlas and AtlasML integration in the artemistest3 environment.
• Enabled the atlas service and added an atlasml section (with enabled: false) in group_vars/artemistests_atlas.yml for Atlas-related test configurations.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch atlas-config-update

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}