[OPIK-6769] [BE] feat: exclude demo data from prompt version creation BI event

[BorisTkachenko]

Details

Prompt version creation emits a prompt_version_created BI event used for product analytics. Versions created for built-in demo prompts were inflating these metrics. This change skips the event when the prompt name matches a known demo prompt, so analytics reflect only real user activity.

• Threads the prompt name through savePromptVersion into trackPromptVersionCreated, which now returns early when the name is in DemoData.PROMPTS.
• Adds support-agent-system to the demo prompt list.

Change checklist

• User facing
• Documentation update

Issues

• Resolves #
• OPIK-6769

AI-WATERMARK

AI-WATERMARK: yes

• Tools: Claude Code
• Model(s): Claude Opus 4.8
• Scope: Implementation and tests
• Human verification: Author reviewed diff and test coverage

Testing

• Added parameterized test shouldCreatePromptVersion__whenDemoPrompt__thenDoesNotEmitEvent (one case per demo prompt name) in PromptResourceTest, verifying no prompt_version_created event is emitted for demo prompts. A sentinel real prompt is created afterward through the same async pipeline; once its event arrives, the absence of the demo event is conclusive.
• Run: mvn test -Dtest=PromptResourceTest

Documentation

N/A

[baz-reviewer]

Should we normalize promptName here or use a case-insensitive check, otherwise DemoData.PROMPTS.contains(promptName) misses migrated casing and emits prompt_version_created for demo data.

Want Baz to fix this for you? Activate Fixer

Other fix methods

Prompt for AI Agents

Before applying, verify this suggestion against the current code. In
apps/opik-backend/src/main/java/com/comet/opik/domain/PromptService.java around lines
557-561, the `trackPromptVersionCreated(...)` method uses
`DemoData.PROMPTS.contains(promptName)` which is case-sensitive. Refactor the guard to
compare in a case-insensitive way by normalizing `promptName` (and/or precomputing a
normalized set from `DemoData.PROMPTS`) before the `contains` check. Also ensure the
normalization handles null/blank safely so demo prompts with different casing never leak
`prompt_version_created` events.

[LifeXplorer]

Looks good!