hotfix: dev Django 실행 환경 복원

[Neibce]

Changelog

• dev Kubernetes에서 Django local 설정 전환을 제거해 /data PVC 경로 사용 복원

Testing

• dev backend/celery/beat의 OJ_ENV 미지정 및 관측 환경 라벨 유지 확인

Ops Impact

• dev overlay 재적용 시 backend/celery 재시작
• DB 마이그레이션 없음

Version Compatibility

• N/A

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cfa8ef2dfd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update the guide after switching dev to production mode

After this removal, the dev deployment inherits OJ_ENV=production from backend/Dockerfile:6, causing backend/oj/settings.py:21-25 to load production settings. However, docs/content/developer/infra/observability-improvement-plan/_index.md:80 still explicitly states that the dev overlay fixes OJ_ENV=dev. This now documents the opposite runtime contract and could lead an operator or future change to restore the setting that broke the /data path; update the guide to describe the inherited production Django mode while retaining the separate dev telemetry labels.

Useful? React with 👍 / 👎.