[AWS::EFS::FileSystem] - [BUG] - Changing `ThroughputMode` in the AWS GUI is not recognized by Drift Detection

### Name of the resource

AWS::EFS::FileSystem

### Issue Description

When you create a `AWS::EFS::FileSystem` using CloudFormation

```yaml
EFSVolume:
Type: AWS::EFS::FileSystem
Properties:
AvailabilityZoneName: !Sub "${AWS::Region}a"
BackupPolicy:
Status: "DISABLED"
```

The default `ThroughputMode` will be `bursting`. Changing `bursting` to `elastic` in the AWS GUI will result in the CloudFormation Stack to be drifted, but this is not recognized by Drift Detection and the Resource is showing up as `Resource drift status: IN_SYNC`

### Expected Behavior

Drift Detection of `AWS::EFS::FileSystem` is working for the `ThroughputMode`.

### Observed Behavior

It's not working.

### Test Cases

1. Create an EFS Volume:

```yaml
EFSVolume:
Type: AWS::EFS::FileSystem
Properties:
AvailabilityZoneName: !Sub "${AWS::Region}a"
BackupPolicy:
Status: "DISABLED"
```

2. Change the `ThroughputMode` to a different value in the AWS GUI
3. Check the Resource Drift in the Drift Detection GUI

Start by creating the AWS::EFS::FileSystem resource with the YAML shown, then change ThroughputMode from bursting to elastic in the AWS GUI and run Resource Drift Detection. Done means Drift Detection reports the resource as drifted instead of IN_SYNC.

Written by the indexing model from the issue text.