Add regression testing job to shared verify workflow

[gontzess]

Summary

• Adds run_regression (boolean, default: true) and connector (string) inputs to the shared verify workflow
• Adds a regression job that calls ConductorOne/baton-regression/.github/workflows/regression.yml@main
• Regression runs when run_regression == true and connector is non-empty
• No impact on existing callers — run_regression defaults to true but regression only runs if connector is provided, which no current caller does

Depends on: ConductorOne/baton-regression#2 (rename workflow file)

Pre-req: baton-regression access_level set to organization (already done)

Test plan

• Verify existing connector verify workflows still pass (no connector input → regression skipped)
• After baton-admin deploys updated verify.yaml with connector input, verify regression runs on known-working connectors

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• .github/workflows/verify.yaml is excluded by none and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch gontzess/add-regression-job

---

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