Added validation for seed password

[NathanDrake007]

Description

Fixes the seed job accepting any value for ADMIN_PASSWORD without validation, which resulted in an admin account that could not be used to log in. The seed job now rejects passwords that don't meet complexity requirements before hashing and writing to the database.

Fixes #3711

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Refactor (non-breaking changes to code which doesn't change any behaviour)
• Test changes (add, refactor, improve or change a test)

What's Changed

• Renamed passwordValidation to ValidatePassword in pkg/validator/validator.go to export it for reuse outside the package
• Added password validation to SeedDatabase in cmd/hatchet-admin/cli/seed/seed.go — the seed job now returns a clear error and exits early if ADMIN_PASSWORD does not meet complexity requirements (8–64 characters, at least one uppercase letter, one lowercase letter, and one number)

[vercel]

@NathanDrake007 is attempting to deploy a commit to the Hatchet Team on Vercel.

A member of the Team first needs to authorize it.

[gregfurman]

While this is technically valid, I'm thinking that we should rather just return a DefaultValidator and pass in an anonymous struct with a password field i.e

validator := validator.NewDefaultValidator()
opts := struct{Password string `json:"password"`}{dc.Seed.AdminPassword}
// Or maybe even just use the already existing CreateUserOpts 👇 
// opts := repository.CreateUserOpts{Password: dc.Seed.AdminPassword} 
err := validator.Validate(opts)
// ...

That way we don't have to expose this function publicly and can just rely on our normal validation mechanism for this check.