refactor(admin-panel): standardize FeatureFlagKey usage

[AMoreaux]

Replaced string-based feature flag keys with the typed FeatureFlagKey enum across the admin panel module and related front-end hooks. This ensures stronger type safety, reduces potential errors, and improves consistency in handling feature flags.

[greptile-apps]

PR Summary

This PR standardizes feature flag handling by implementing a strongly-typed FeatureFlagKey enum across the admin panel module, replacing string-based keys for improved type safety and consistency.

• Refactored useFeatureFlagsManagement.ts hook to use typed FeatureFlagKey enum with optimistic updates and error rollback
• Updated admin-panel.service.ts to handle enum-based feature flag keys in updateWorkspaceFeatureFlags method
• Modified FeatureFlag.ts type definition to enforce strict typing with FeatureFlagKey enum from GraphQL types
• Simplified admin-panel.resolver.ts by removing redundant enum lookups and using direct feature flag key passing

_{4 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[github-actions]

	Fails
🚫	node failed.

Log

�[31mError: �[39m SyntaxError: Unexpected token C in JSON at position 0
    at JSON.parse (<anonymous>)
�[90m    at parseJSONFromBytes (node:internal/deps/undici/undici:5584:19)�[39m
�[90m    at successSteps (node:internal/deps/undici/undici:5555:27)�[39m
�[90m    at fullyReadBody (node:internal/deps/undici/undici:1665:9)�[39m
�[90m    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)�[39m
�[90m    at async specConsumeBody (node:internal/deps/undici/undici:5564:7)�[39m
danger-results://tmp/danger-results-619f6e80.json

Generated by 🚫 dangerJS against bf48ff4