How to make synth execution fail when using deprecated properties and constructs

[sakurai-ryo]

Hi all,

I want to make synth execution fail when using a deprecated property or construct.
For example, consider the following code

export class TestStack extends Stack {
  constructor(scope: Construct, id: string, props: StackProps) {
    super(scope, id, props);

    const accessLogBucket = s3.Bucket.fromBucketName(this, 'TargetBucket', 'access-log-bucket');

    new s3.Bucket(this, 'TestS3Bucket', {
      encryption: s3.BucketEncryption.UNENCRYPTED, // @deprecated annotation
      serverAccessLogsBucket: accessLogBucket, // addWarningV2 called inside the Bucket class constructor
      serverAccessLogsPrefix: 'logs/',
    });
  }
}

When I run synth with this code, I get two warnings as follows

[WARNING] aws-cdk-lib.aws_s3.BucketEncryption#UNENCRYPTED is deprecated.
  S3 applies server-side encryption with SSE-S3 for every bucket
that default encryption is not configured.
  This API will be removed in the next major release.

[Warning at /TestStack1/TestS3Bucket] Unable to add necessary logging permissions to imported target bucket: TestStack1/TargetBucket [ack: @aws-cdk/aws-s3:accessLogsPolicyNotAdded]

Found warnings (--strict mode)

The first warning is that BucketEncryption.UNENCRYPTED has a deprecated annotation in TSDoc.
The second warning is a warning in the CDK code using methods such as addWarningV2.

If I use the --strict option of synth command, only the second warning will be treated as a failure.
The following code successfully executes synth even when the --strict option is used.

export class TestStack extends Stack {
  constructor(scope: Construct, id: string, props: StackProps) {
    super(scope, id, props);

    new s3.Bucket(this, 'TestS3Bucket', {
      encryption: s3.BucketEncryption.UNENCRYPTED, // @deprecated annotation
    });
  }
}

In this case, for example, if I use BucketEncryption.UNENCRYPTED, is there any way to make the synth execution fail?
I know that it can be detected by using a mechanism other than CDK, such as eslint-plugin-deprecation, but I would like to know if there is such a way with the CDK mechanism.