fix: validate uuid on admin methods and fix wrong factor in delete_factor method

[grdsdev]

This pull request introduces UUID validation for user-related operations in both the asynchronous and synchronous versions of the gotrue_admin_api module. It ensures that invalid UUIDs are caught early, preventing unnecessary API calls. Additionally, new tests have been added to verify this behavior.

UUID Validation Enhancements:

• Added a new helper function is_valid_uuid in supabase_auth/helpers.py to validate UUIDs.
• Introduced a _validate_uuid method in both supabase_auth/_async/gotrue_admin_api.py and supabase_auth/_sync/gotrue_admin_api.py to validate UUIDs before making API requests. [1] [2]
• Updated all relevant methods (get_user_by_id, update_user_by_id, delete_user, _list_factors, _delete_factor) in gotrue_admin_api to call _validate_uuid for input validation. [1] [2] [3] [4] [5] [6] [7] [8]

Test Coverage:

• Added tests in tests/_async/test_gotrue_admin_api.py to verify that invalid UUIDs raise ValueError in all relevant methods.
• Added equivalent tests in tests/_sync/test_gotrue_admin_api.py for the synchronous API.

Other Changes:

• Updated imports in supabase_auth/_async/gotrue_admin_api.py and supabase_auth/_sync/gotrue_admin_api.py to include is_valid_uuid. [1] [2]
• Added uuid import in supabase_auth/helpers.py to support UUID validation.

[staaldraad]

nice! 💪🏼