chore: remove orphaned _devenvironment/Dockerfile

[fronzec]

What

Removes fr-batch-service/_devenvironment/Dockerfile, an unreferenced (dead) file.

Why

• _devenvironment/docker-compose.yml only defines the mysql service and has no build: key — it never builds this Dockerfile.
• Nothing else in the repo references it (task up/down run podman-compose against that compose file, which doesn't touch it).
• As written it could not build anyway: COPY . . && RUN mvn clean verify runs against the _devenvironment directory, which contains only the compose file and this Dockerfile — no pom.xml.

It also happened to be the only Maven base-image pin that diverged from the real build image: this file used maven:3.9.12-eclipse-temurin-21 while fr-batch-service/Dockerfile uses maven:3.9-eclipse-temurin-21. Removing it leaves fr-batch-service/Dockerfile as the single source of truth for the build image.

Risk

None — the file is unused. CI is unaffected (the real image build lives in fr-batch-service/Dockerfile, built by docker / docker-dry-run).

[coderabbitai]

Warning

Review limit reached

@fronzec, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 28 minutes and 4 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 14ebf911-0702-4d47-adfb-837e5a2d6198

📥 Commits

Reviewing files that changed from the base of the PR and between 253f166 and 8087e4c.

📒 Files selected for processing (1)

• fr-batch-service/_devenvironment/Dockerfile

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/remove-orphan-dockerfile

---

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