fix: prevent creating new buckets with the name 'public'

[itslenny]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

Users can create buckets named "public" using the API

What is the new behavior?

A 400 error is thrown if a user tries to create a bucket named "public" via API or S3 protocol

The studio UI already prevents using "public" as a bucket name. This change mirrors that behavior in the API.

Additional context

A bucket with the name "public" causes issues with our api route resolution.

For example, if an object's path is public/something/file.png:

A request to /object/info/:bucketName/* routes to /object/info/public/:bucketName/* and returns a BUCKET NOT FOUND error for the bucket "something"

Also, a request to /object/:bucketName/* routes to /object/public/:bucketName/* and results in the same error

[coveralls]

Pull Request Test Coverage Report for Build 15471315258

Details

• 4 of 4 (100.0%) changed or added relevant lines in 1 file are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.01%) to 77.806%

---

Files with Coverage Reduction	New Missed Lines	%
src/internal/database/tenant.ts	2	82.3%

Totals
Change from base Build 15466403204:	-0.01%
Covered Lines:	17396
Relevant Lines:	22195

---

💛 - Coveralls