RHCLOUD-50147: Rename and require Splunk token field

[platex-rehor-bot]

Description

Renames the Splunk integration's secret token field from "Secret token" to "Splunk HEC token" and makes it required. The change applies to both the integration creation wizard (data-driven forms) and the Formik-based edit form. Whitespace-only input is treated as empty, consistent with the backend validation being added in RHCLOUD-50144. No other integration types are affected.

RHCLOUD-50147

---

Screenshots

No visual screenshots — this is a label rename and validation change on an existing text field.

---

Checklist ☑️

• PR only fixes one issue or story
• Change reviewed for extraneous code
• UI best practices adhered to
• Commits squashed and meaningfully named
• All PR checks pass locally (build, lint, test, E2E)

• (Optional) QE: Needs QE attention (OUIA changed, perceived impact to tests, no test coverage)
• (Optional) QE: Has been mentioned
• (Optional) UX: Needs UX attention (end user UX modified, missing designs)
• (Optional) UX: Has been mentioned

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b1ba9126-925c-4e01-8c47-906931a9908c

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Chromatic Build

	Link
Storybook	https://6980bce13ca67d03fef6d1f0-gvbvcijkdf.chromatic.com/
Build	https://www.chromatic.com/build?appId=6980bce13ca67d03fef6d1f0&number=557

[aferd]

looks like the konflux build failed due to the e2e tests. @platex-rehor-bot

[platex-rehor-bot]

/retest

[platex-rehor-bot]

@aferd Thanks for flagging! I investigated the e2e failure:

• Not caused by this PR — none of the Playwright specs test Splunk integration creation. The PR only changes the Splunk token field label/validation in the wizard and Formik form.
• Build passes — verified locally with npm ci + npm run build (the committed lockfile correctly includes all deps).
• Unit tests pass — all 96 integration-related tests pass, including the 7 new schema validation tests.
• Likely flaky — PR feat(RHCLOUD-50186): Adopt isKesselEnabled for v1/v2 permission detection #1052 (same master, same .tekton config, same set of specs) passed e2e. The pipeline runs all 7 Playwright specs with 180s timeout and 2 retries, and module federation navigation can be slow in Konflux.

I triggered a /retest to retry the pipeline. If it fails again, I can investigate which specific spec is failing (Konflux logs returned 401 this cycle, so I couldn't read the failure details).

[aferd]

/retest

[platex-rehor-bot]

@aferd Thanks for the retest! Unfortunately, it failed again in ~1m42s — that's too fast to even reach e2e tests, so it's likely a Konflux infrastructure issue (provisioning/image pull).

I also checked PR #1049 — its Konflux pipeline is failing too, confirming this is a systemic issue affecting the repo, not something caused by this PR's changes.

I've rebased the branch on latest master (picking up #1055) to trigger a fresh pipeline run with a new commit SHA. Hopefully the new run fares better. All other checks (build, unit tests, CodeQL, Snyk, linting) continue to pass.

[aferd]

@platex-rehor-bot please rebase again, the upstream tests should be fixed.

[platex-rehor-bot]

Thanks @aferd! Rebased to pick up the upstream fix — new commit SHA 86969e1. Fresh Konflux pipeline should be triggered now. 🤞