📝 Description

This pull request updates the logic for generating runbook folder options in the runbook rule form, allowing the UI to present all nested folder paths for each runbook file instead of just the top-level folder. This improves the granularity and flexibility of folder-based selections in the runbook rule setup.

🚀 Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Style/UI update
• ♻️ Code refactor
• ⚡ Performance improvement
• ✅ Test update
• 🔧 Build configuration change
• 🧹 Chore

📋 Changes Made

• The extract-folder function is replaced with extract-all-folders, which extracts all possible folder paths from a runbook file name, supporting nested folders (e.g., 'postgres-demo/queries/file.runbook.sql' yields both 'postgres-demo/' and 'postgres-demo/queries/').
• The folder option generation logic in generate-runbook-options is updated to use all extracted folders, ensuring that each unique folder path is presented as a selectable option, and preventing duplicate folder entries in the options list.

🧪 Testing

Test Configuration:

• Browser(s): Chrome
• OS: MacOS

Tests performed:

• Unit tests pass
• Integration tests pass
• Manual testing completed

📸 Screenshots

✅ Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes
• I have checked my code and corrected any misspellings