Added a fix for handling invalid_schema_error returning with invalid status value for bucket lifecycle configuration rule

[achouhan09]

Explain the changes

1. This fix ensures that when an INVALID_SCHEMA_PARAMS error occurs due to an incorrect Status value (other than "Enabled" or "Disabled") in a bucket lifecycle configuration rule, the appropriate AWS S3 error (MalformedXML) is returned.

Below is the aws output:

Issues: Fixed #xxx / Gap #xxx

1. Fixed: NSFS | S3 | Lifecycle: Invalid rule status returns http error 500 #8553

Testing Instructions:

1. create s3 backingstore>bucketclass>obc.
2. Apply below policy on the bucket created with obc:
   $ AWS_ACCESS_KEY_ID=<access-key> AWS_SECRET_ACCESS_KEY=<secret-key> aws s3api --no-verify-ssl --endpoint-url <endpoint-url> put-bucket-lifecycle-configuration --bucket <bucket-name> --lifecycle-configuration '{ "Rules": [ { "ID": "rule_id", "Status": "enabled", "Filter": { "Prefix": "test/" }, "Expiration": { "Date": "2020-01-02T00:00:00.000Z" } } ] }'
3. Check for the similar error as AWS S3:
   An error occurred (MalformedXML) when calling the PutBucketLifecycleConfiguration operation: The XML you provided was not well-formed or did not validate against our published schema

• Tests added

[shirady]

LGTM