S3 supported object name validation coverage

[ckulal]

S3 supported object name validation coverage:

Adds RGW coverage for S3 object key naming against the 
Amazon S3 object key guidelines.

The test creates an RGW user and bucket, then PUT/GET/DELETE objects whose keys exercise each AWS category. 

Categories

• Safe characters — alphanumerics, ! - _ . * ' ( ), documented AWS examples, prefix/delimiter keys, trailing period, and case-sensitive names

• Period-only path segments — . / .. segments that remain valid via the S3 API (./file.txt, folder/../file.txt, hidden/backup names, AWS valid relative path videos/2014/../../video1.wmv, key .)


• Special handling — & $ @ = ; / : + space , ?, leading/trailing/consecutive slashes, non-ASCII UTF-8, and ASCII 00–1F / 7F (NUL is expected to fail)


• Characters to avoid — \ { } ^ % \ ] " > [ ~ < # |` and ASCII 128–255; still expected to succeed over the API


• Hard limits — empty key (reject), 1024-byte UTF-8 max (accept), 1025 bytes (reject), multibyte UTF-8 at/over the limit, and key soap (allowed with path-style)


• Confirm safe, period-segment, special-handling, and avoid keys PUT/GET successfully

• Confirm empty key, keys over 1024 UTF-8 bytes, and NUL are rejected

• Confirm objects and the test bucket are cleaned up

Pass log: http://magna002.ceph.redhat.com/ceph-qe-logs/obj_name_validation/test_object_name_validation.console.log2

[TejasC88]

LGTM