feat(logs): allow viewing and editing LogPipeline processors

[suvvvv]

What

On the LogPipeline detail page, the Processors table only allowed delete — isEditable was hardcoded false. There was no way to view or change an existing processor's configuration short of deleting and recreating it.

isEditable was off for a real reason: a processor's configuration is polymorphic per type (SeverityRemapper / AttributeRemapper / CategoryProcessor), so the generic ModelForm edit can't render it. Creation already uses a custom ProcessorForm for that reason.

This adds view + edit by reusing that same custom form in edit mode:

ProcessorForm

• New optional initialProcessor prop. When provided, the form opens pre-filled from the processor's saved configuration (the inverse of buildConfiguration), and on save calls ModelAPI.updateById instead of create, preserving sortOrder.
• A small parseConfiguration helper accepts the config as either an object or a JSON-string literal (both shapes occur in storage).
• Modal title and submit label switch between "Add Processor" / "Create Processor" and "Edit Processor" / "Save Changes".

PipelineView

• Fetches configuration / isEnabled / sortOrder via selectMoreFields so the row item is complete.
• Adds an Edit action button per row that opens the form for that processor; the "Add Processor" button clears any edit state first.

Opening a processor for edit also covers the "view configuration" ask from the issue, since the form shows the full current config.

Why

Resolves the "cannot view or edit processor config" problem in #2516 — users no longer have to delete and recreate a processor to change it.

Testing

• npx tsc --noEmit — clean for both changed files.
• eslint + Prettier — clean.

Note: this is a UI change and I don't currently have the full local stack running, so it has not yet been verified in a browser. The logic is type-checked and lint-clean; happy to record a quick screen capture once I have the dashboard up, or if a maintainer can sanity-check the edit flow.

Refs #2516

[simlarsen]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.