🧪 fix: standardize BDD test execution across all feature suites

- Fixed path resolution in test setup to handle both feature-specific and multi-feature execution
- Standardized stopOnFailure=false for all feature tests to ensure consistent behavior
- Removed @todo tag from implemented Configuration validation scenario
- Ensured GODOG_TAGS=todo go test ./features/X/... and FEATURE=X go test ./features/ run identical tests

All feature suites (jwt, auth, greet, health, config) now behave consistently regardless of execution method.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>

features/jwt/jwt_secret_retention.feature

@@ -83,7 +83,6 @@ Feature: JWT Secret Retention Policy
     And the old token should still be valid during retention period
     And both tokens should work until retention period expires
 
-  @todo
   Scenario: Configuration validation
     Given I set retention factor to 0.5
     When I try to start the server