fix: add bucket name length constraint

[TylerHillery]

What kind of change does this PR introduce?

Bug fix, restricting bucket name length to a max of 63 characters to adhere to S3 Bucket naming rules

What is the current behavior?

No restrictions on the length of bucket name

What is the new behavior?

Added Postgres buckets name length check constraint and updated isValidBucketName function. Also added test in bucket.test.ts to verify 400 is being returned when issuing a POST request with name longer than 63 characters.

Additional context

I updated the fromDBerror switch statement to include the new pgError.code for the buckets name length check constraint. The ERRORS.InvalidBucketName error requires the bucket name I opted to parse it from the pgError.detail Example pgError.detail:

'Failing row contains (aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa, null, 2025-05-03 21:04:15.907656+00, 2025-05-03 21:04:15.907656+00, f, f, null, null, null).'

[TylerHillery]

Updated PR to change the max bucket name length to 100 to stay backwards compatible

[TylerHillery]

We can't add postgres constraint if there is data already in the table that violates the constraint. Putting this PR back in draft while I think of a way we can implement this while maintaining compatibility with buckets that already violate the constraint.