🐛 fix: resolve port conflicts and state pollution in test validation

- Remove FIXED_TEST_PORT and BDD_SCHEMA_ISOLATION from validate-test-suite.sh
- Change go test ./features/... to go test ./features to avoid duplicate runs
- Update recommendations to prioritize investigation over flaky tagging
- Remove @flaky tags now that root causes are fixed

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

features/auth/user_authentication.feature

@@ -31,7 +31,6 @@ Feature: User Authentication
     And I should receive a valid JWT token
     And the token should contain admin claims
 
-  @flaky
   Scenario: User registration
     Given the server is running
     When I register a new user "newuser_" with password "newpass123"
@@ -46,7 +45,6 @@ Feature: User Authentication
     Then the password reset should be allowed
     And the user should be flagged for password reset
 
-  @flaky
   Scenario: User completes password reset
     Given the server is running
     And a user "resetuser" exists and is flagged for password reset
@@ -111,7 +109,6 @@ Feature: User Authentication
     Then the authentication should fail
     And the response should contain error "invalid_credentials"
 
-  @flaky
   Scenario: Multiple consecutive authentications
     Given the server is running
     And a user "multiuser" exists with password "testpass123"
@@ -132,7 +129,6 @@ Feature: User Authentication
     Then the token should be valid
     And it should contain the correct user ID
 
-  @flaky
   Scenario: Authentication with expired JWT token
     Given the server is running
     And a user "expireduser" exists with password "testpass123"

features/jwt/jwt_secret_rotation.feature

@@ -11,7 +11,6 @@ Feature: JWT Secret Rotation
     Then the authentication should be successful
     And I should receive a valid JWT token signed with the primary secret
 
-  @flaky
   Scenario: Token validation with multiple valid secrets
     Given the server is running with multiple JWT secrets
     And a user "tokenuser" exists with password "testpass123"
@@ -22,7 +21,6 @@ Feature: JWT Secret Rotation
     Then the token should be valid
     And it should contain the correct user ID
 
-  @flaky
   Scenario: Secret rotation - adding new secret while keeping old one valid
     Given the server is running with primary JWT secret
     And a user "rotateuser" exists with password "testpass123"
@@ -42,7 +40,6 @@ Feature: JWT Secret Rotation
     Then the authentication should fail
     And the response should contain error "invalid_token"
 
-  @flaky
   Scenario: Graceful secret rotation with user continuity
     Given the server is running with primary JWT secret
     And a user "gracefuluser" exists with password "testpass123"