[AWS::SSM::ServiceSetting] - [BUG] - False-positive drift when specifying the SSM "System" default value

### Name of the resource

Other

### Resource Name

AWS::SSM::ServiceSetting

### Issue Description

This drift is similar to https://github.com/aws-cloudformation/cloudformation-coverage-roadmap/issues/1725 in which Drift Detection is unable to find the resource and marks it as

> Resource drift status
> DELETED

### Expected Behavior

WIP

### Observed Behavior

WIP

### Test Cases

```yaml
AWSTemplateFormatVersion: 2010-09-09
Description: Test

Resources:
# https://docs.aws.amazon.com/systems-manager/latest/APIReference/API_UpdateServiceSetting.html
SSMServiceSetting:
Type: AWS::SSM::ServiceSetting
Properties:
SettingId: /ssm/appmanager/appmanager-enabled
SettingValue: "False" # Default "System" value
```

```json
{
"ServiceSetting": {
"SettingId": "/ssm/appmanager/appmanager-enabled",
"SettingValue": "False",
"LastModifiedDate": "20...",
"LastModifiedUser": "System",
"ARN": "arn::ssm:::servicesetting/ssm/appmanager/appmanager-enabled",
"Status": "Default"
}
}
```

### Other Details

_No response_

Start with the YAML test case for AWS::SSM::ServiceSetting and compare it with the returned ServiceSetting JSON, including the System default value and Default status. Review the related drift issue #1725, then establish the expected drift status and verify that the false DELETED result is resolved.

Written by the indexing model from the issue text.