refactor: use ansible.posix 2.1.X for EL7 compatibility [citest_skip]

[richm]

The recently released ansible.posix 2.2.0 does not work on EL7.
Pin the version of ansible.posix to 2.1.X.

NOTE: Even though this role might not support EL7, this update
is applied to all system roles for consistency. Plus, when this
role is part of the system roles collection, all roles must use
the same version of ansible.posix - there is no way for a role
which is part of a collection to use a different version of a
dependency than the version used by the other roles.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Pins the ansible.posix collection dependency to version 2.1.0 to maintain compatibility with EL7 while keeping existing community.general constraints unchanged.

File-Level Changes

Change	Details	Files
Constrain ansible.posix collection to a specific compatible version.	Add an explicit version constraint for the ansible.posix collection set to 2.1.0. Leave the community.general collection version range as-is, maintaining existing compatibility guarantees.	meta/collection-requirements.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. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

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 - I've left some high level feedback:

• Consider adding a brief inline comment in collection-requirements.yml next to the ansible.posix version pin to document the EL7 compatibility reason, so future updates don’t inadvertently break EL7 support.
• If EL7 compatibility allows some flexibility, you might want to specify a compatible version range (e.g., <2.2.0) instead of pinning to exactly 2.1.0 to ease future maintenance while still avoiding the known-bad release.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider adding a brief inline comment in `collection-requirements.yml` next to the `ansible.posix` version pin to document the EL7 compatibility reason, so future updates don’t inadvertently break EL7 support.
- If EL7 compatibility allows some flexibility, you might want to specify a compatible version range (e.g., `<2.2.0`) instead of pinning to exactly `2.1.0` to ease future maintenance while still avoiding the known-bad release.

---

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.}

[coderabbitai]

Warning

Rate limit exceeded

@richm has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 9 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9ee086e4-f9f4-4ef1-a427-a82bd68e517c

📥 Commits

Reviewing files that changed from the base of the PR and between 3dd2fe9 and 6e379cc.

📒 Files selected for processing (1)

• meta/collection-requirements.yml

---

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

[Jakuje]

not sure whats up with the CI though.

[spetrosi]

not sure whats up with the CI though.

rate limit exceeded because PRs to all repos got pushed at once. Next time we'll use [citest_skip] to make coderabbit ignore such PRs.