feat(editorconfig): add naming rules for static readonly fields

[samtrion]

Summary by CodeRabbit

Release Notes

• Chores
  • Introduced comprehensive naming conventions for static readonly fields to enforce consistent PascalCase capitalization standards, strengthening automated code style enforcement and consistency throughout the project.
  • Updated and refined existing constant field naming rules to improve code quality, maintain consistency standards, and ensure alignment with development conventions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: daa436e3-b99b-4a94-ae5e-783cef674122

📥 Commits

Reviewing files that changed from the base of the PR and between 0c0008d and 11dac94.

📒 Files selected for processing (1)

• src/NetEvolve.Defaults/configurations/editorconfig.txt

---

Walkthrough

Introduces EditorConfig naming conventions for static readonly fields requiring pascal_case capitalization. Updates the existing constants rule's style reference. Changes add six new naming configuration entries and modify one existing entry across a single configuration file.

Changes

Cohort / File(s)	Summary
EditorConfig Naming Rules src/NetEvolve.Defaults/configurations/editorconfig.txt	Added new naming style, symbols, and rule for static readonly fields with pascal_case capitalization (6 entries). Updated existing const rule's style reference from all_elements to all_const.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Poem

🐰 Static readonly fields now align,
With pascal_case rules so fine,
EditorConfig shines with design,
Naming conventions divine! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding naming rules for static readonly fields to the editorconfig configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (0c0008d) to head (11dac94).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@     Coverage Diff     @@
##   main   #324   +/-   ##
===========================
===========================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.