chore: Remove UUID validation

[kofimokome]

No description provided.

[sourceant]

Code Review Summary

✨ This pull request primarily modifies the validation and OpenAPI documentation for the client_id field across multiple API endpoints (Category, Group, Party, Transaction, Transfer, Wallet). Specifically, the client_id validation has been relaxed from requiring a uuid format to accepting any string.

🚀 Key Improvements

• Consistency in validation rule update for client_id across all related controllers and the OpenAPI documentation.

💡 Minor Suggestions

• Clarify the precise nature and intended format of client_id to ensure long-term data consistency and prevent potential downstream issues related to its format. A note in design documentation would be helpful.

🚨 Critical Issues

• If client_id is unequivocally meant to be a UUID for system-wide uniqueness and integrity, then changing its validation to string represents a critical relaxation of a core data constraint. This could lead to data corruption, silent failures, or unexpected behavior in systems that expect a UUID. This needs immediate verification of the business requirement and potentially a reversion if uuid is indeed the correct format.

[sourceant]

Review complete. See the overview comment for a summary.

[sourceant]

Review complete. See the overview comment for a summary.