[Drift Detection] - [BUG] - Stack shows drift status IN_SYNC, but resource are in status MODIFIED

### Name of the resource

Other

### Resource Name

_No response_

### Issue Description

After running a fresh drift detection on a CFN stack, the drift status shows the state "IN_SYNC", but while checking the resources tab there are drifted resources. That seems to be a bug. Not all of our stacks are affected.

### Expected Behavior

Stack drift status show "DRIFTED" in case resources of the stack are in status "MODIFIED" (are drifted due to out-of-band changes) - in Console and API.

### Observed Behavior


Stack drift status show "DRIFTED" in case resources of the stack are in status "MODIFIED" (are drifted due to out-of-band changes) - in Console and API.

### Test Cases

For the above CloudFormation stack I've triggered ‘Detect Drift’ (+ wait, to ensure drift detection finished). In the resources tab, you can see two resources are in ‘MODIFIED’ state, but the overall stack drift status shows as ‘IN_SYNC’. We confirmed this via CLI/API and Console.

There is no clear repo/test-case known yet. It's a "backend-issue" in CFN drift detection.

### Other Details

_No response_

Start by reproducing the issue with CloudFormation drift detection, then compare the stack status with resource statuses in the console and through the CLI/API. The issue provides no repository, file, or test case; done means the stack reports DRIFTED when resources are MODIFIED in both the console and API.

Written by the indexing model from the issue text.