condo fix(condo): DOMA-11360 fix translate in classifiers

Summary by CodeRabbit

New Features
- Expanded ticket classification system with new categories and problem classifiers in Spanish, enhancing options for building management and maintenance.
Refactor
- Renamed ticket classification terms from "Counters" to "Meters" across multiple languages for consistency.
- Removed outdated ticket place options to streamline classification choices, offering a clearer selection process.
Bug Fixes
- Addressed inconsistencies in ticket classification terminology across different languages.

Mar 28 '25 14:03 tolmachev21

Walkthrough

The changes update localization files across English, Spanish, and Russian. The key identifiers for the ticket category and problem classifiers have been renamed from "COUNTERS" to "METERS" while retaining their original display values. In addition, several ticket place classifier keys have been removed from the English and Spanish files, streamlining the classification system.

Changes

File(s)	Change Summary
`apps/.../en.json`, `apps/.../es.json`, `apps/.../ru.json`	Renamed keys: `"ticket.category.classifier.COUNTERS.name"` → `"ticket.category.classifier.METERS.name"` and `"ticket.problem.classifier.COUNTERS.name"` → `"ticket.problem.classifier.METERS.name"` across all files.
`apps/.../en.json`, `apps/.../es.json`	Removed keys under `ticket.place.classifier`: `IT_SERVICES`, `SECURITY`, `COURTYARD`, `APARTMENT`, `RECEIPT`, `PARKING`, `ENTRANCEWAY`, `PAVEMENTS_ROADS_LAWNS`, `DOCUMENTS`, `FACADES`, `ATTICS_BASEMENTS`, `ROOFING`, `NON_RESIDENTIAL_PREMISES`, and `FEEDBACK_ON_WORK`.

Suggested reviewers

dkoviazin
AleX83Xpert
YEgorLu
toplenboren

Poem

I'm a hopping rabbit with a playful beat,
Watching keys transform in each locale so neat.
COUNTERS now wear the name of METERS with flair,
And extra place keys vanished into thin air.
With a hop and a smile, I celebrate this spree—
Carrots and code make a delightful jubilee! 🥕🐇

✨ Finishing Touches

[ ] 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai plan to trigger planning for file edits and PR creation.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json