feat: disable policy feature when 403 or error when fetching and parsing bucket policy

[ddecrulle]

No description provided.

[garronej]

I'd rather see:

try{
}catch(error){
    if( !(error instanceof S3ServiceException)){
        throw error;
    }
    switch(...
}

The reasoning is that we should be consistent with our error management policies.
If we wheren't handling S3ServiceException we would let the exception stop the execution.

As of now, any other type of exception that might be thrown here is unexpected and we should adress it.

[garronej]

Here again I'd rather have a finer handling of the exceptions.

let parsedPolicy;

try{
   parsedPolicy = s3BucketPolicySchema.parse(JSON.parse(sendResp.Policy));
}catch(error){
     console.error("failed to parse policy", String(error))
     return {
            isBucketPolicyAvailable: false,
            bucketPolicy: undefined,
            allowedPrefix: []
     };
}

let allowedPrefix;

try{
   allowedPrefix = ...
}catch(error){
     console.error("Failed to extract allowed prefix from policy", String(error));
     return { ... };
}

  return {
       isBucketPolicyAvailable: true,
       bucketPolicy: parsedPolicy,
       allowedPrefix
    };

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE