Cloud SRE Agents - AWS Account ID filtering/routing does not work

**Describe the bug**
Profile filters for AWS account ID do not work.

**To Reproduce**
Steps to reproduce the behavior:
1. Create a profile filter for AWS Account ID is
2. Simulate a problem where aws.account.id is set in problem. For me, I simply took a process down on a EC2 server, and had a process availability rule

**Expected behavior**
I expected the problem to route to AWS DevOps Agent because the problem event contains an array of values for aws.account.id

**Additional context**
I think the issue is the AWS profile is set to do something like this in DQL

| filter aws.account.id == "123456789012"

However, on a problem event the actual data is an array, so this will always be false

aws.account.id: ["123456789012"]

"123456789012" is not equal to ["123456789012"]

This also extends to other filters. For Dynatrace's pre-built alerts (service entities, host entities, process entities) how are we supposed to route by aws account id?

Start by inspecting the AWS profile filter and the generated DQL for array-valued aws.account.id. Reproduce the issue with the described EC2 process-availability scenario, then verify that routing matches the AWS account ID and determine whether the other pre-built entity filters have the same behavior.

Written by the indexing model from the issue text.