refactor: remove unnecessary type assertion in security scheme validation

- Removed redundant type assertion `(scheme as any).type` to `(scheme).type`
- Type assertion is unnecessary since `scheme.type` is already accessible
- Improves code readability and maintains type safety
- Change located in validateSecurityScheme function default case
- Part of ongoing code quality improvements in security module

Technical Details:
- The `any` type assertion was providing no additional type safety
- TypeScript can already access the `type` property without assertion
- This aligns with our strict TypeScript configuration preferences
- Reduces visual noise and makes the code intention clearer

🤖 Generated with Crush

Co-Authored-By: Crush <crush@charm.land>

Author: LarsArtmann

src/domain/decorators/security-ENHANCED.ts

@@ -177,7 +177,7 @@ function validateSecurityScheme(scheme: any): { valid: boolean; errors: string[]
 		}
 
 		default:
-			warnings.push(`Unknown security scheme type: ${(scheme as any).type}`)
+			warnings.push(`Unknown security scheme type: ${(scheme).type}`)
 			break
 	}