Fluxnova BPMN Linting Plugin

### Description of Problem

Fluxnova teams rely on BPMN diagrams as executable artifacts rather than simple documentation. However, there is currently no automated way to validate BPMN models against agreed‑upon quality, style, and best‑practice rules during design time.

This leads to several recurring problems:

- Inconsistent BPMN modeling standards across teams and projects
- Hard‑to‑maintain or error‑prone diagrams, often caught late in the development lifecycle
- Manual reviews that are time‑consuming, subjective, and easy to overlook
- Limited early feedback for modelers using BPMN tools, resulting in rework downstream

Without a linting mechanism, BPMN quality checks are ad-hoc and reactive rather than standardized and proactive.

### Potential Solutions

Introduce a BPMN linting plugin for Fluxnova that automatically analyzes BPMN models and flags issues such as modeling errors, anti‑patterns, and violations of internal standards.

A potential starting point is the following open‑source project, which can be adapted in line with our [plugins strategy](https://github.com/finos/fluxnova-bpm-platform/discussions/139): https://github.com/camunda/camunda-modeler-custom-linter-rules-plugin

**Proposed approach**

- Create feature branch in fluxnova-plugins GitHub repository
- Copy over Camunda custom linter plugin, modifying it as appropriate to work with Fluxnova
- Define custom BPMN linting rules, for example:
- Naming conventions for processes, tasks, and events
- Detection of unused, unreachable, or overly complex elements
- Enforcement of modeling best practices (e.g. event usage, gateway semantics)
- Allow for rule configurability so teams can enable/disable or tune rules as standards evolve
- Integrate feedback directly into the modeling experience to provide early, actionable guidance

This would improve BPMN quality, reduce review overhead, and promote consistent modeling practices across Fluxnova projects.