[BB-1723] Add account-status-lifecycle-test action for testing enable/disable account operations

[sergiocorral-conductorone]

AI Description

Adds a new GitHub Action to test account status lifecycle changes (enable/disable) for baton connectors.

Features:

• Tests disable and enable account actions with automatic verification
• Supports multiple test flows: disable-enable, enable-disable, enable-only, disable-only
• Configurable action names and parameter names for different connector implementations
• Validates status changes using baton-sdk UserTrait status checks

Inputs:

• connector: Connector binary to test (required)
• account-id: Account ID to test status changes (required)
• enable-action-name: Custom enable action name (optional, default: "enable_user")
• disable-action-name: Custom disable action name (optional, default: "disable_user")
• id-parameter-name: Custom parameter name (optional, default: "user_id")
• test-flow: Test flow to execute (optional, default: "disable-enable")

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (3)

• actions/account-status-lifecycle-test/README.md is excluded by none and included by none
• actions/account-status-lifecycle-test/account-status-lifecycle-test.sh is excluded by none and included by none
• actions/account-status-lifecycle-test/action.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.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sergiocorral/account-status-test

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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