## SQS to Lambda - the source_arn does not contain the correct region for the source

An SQS queue and lambda function are provisioned in us-west-2 regiona. An event source mapping exists to enable SQS to Lambda triggers.  When a message arrives in the SQS queue, localstack compares the source_arn for the queue with the ARN in the EventSourceMapping (if they match, then the lambda is invoked).  However, the source ARN for the queue incorrectly contains `us-east-1` region, and so does not match the EventSourceMapping ARN, which correctly contains `us-west-1`

### SQS Queue ARN contains us-west-2:
```
{
    "Attributes": {
        "QueueArn": "arn:aws:sqs:us-west-2:000000000000:local-queue"
    }
}
```

### Lambda function ARN contains us-west-2:
```
{
    "Functions": [
        {
            "FunctionName": "local-lambda",
            "FunctionArn": "arn:aws:lambda:us-west-2:000000000000:function:local-lambda",
        }
    ]
}
```

### EventSourceMapping refers to the correct ARNs:
```
{
    "EventSourceMappings": [
        {
            "EventSourceArn": "arn:aws:sqs:us-west-2:000000000000:local-queue",
            "FunctionArn": "arn:aws:lambda:us-west-2:000000000000:function:local-lambda",
        }
    ]
}
```

### When an SQS message is received in local-queue, the source ARN is incorrect:
```
Found 0 source mappings for event from SQS queue arn:aws:sqs:us-east-1:000000000000:local-queue: []
```

### Additional detail

Sending a message using Java client with region us-west-2, source_arn contains us-east-1

When sending a message using AWS CLI, changing the --region will also change the region in the source_arn.

### Expected behavior
The region in the source_arn should match the region that the resource was created in, OR, the event source mapping should not expect region to match

Relevant for event source mapping: get_event_sources in localstack/services/awslambda/lambda_api.py
from localstack.services.awslambda.lambda_executors import (
    LAMBDA_RUNTIME_PYTHON27,
    LAMBDA_RUNTIME_PYTHON36,
    LAMBDA_RUNTIME_NODEJS,
    LAMBDA_RUNTIME_NODEJS610,
    LAMBDA_RUNTIME_NODEJS810,
    LAMBDA_RUNTIME_JAVA8,
    LAMBDA_RUNTIME_JAVA11,
    LAMBDA_RUNTIME_DOTNETCORE2,
    LAMBDA_RUNTIME_DOTNETCORE21,
    LAMBDA_RUNTIME_GOLANG,
    LAMBDA_RUNTIME_RUBY,
    LAMBDA_RUNTIME_RUBY25,
    LAMBDA_RUNTIME_CUSTOM_RUNTIME)
from localstack.utils.common import (to_str, load_file, save_file, TMP_FILES, ensure_readable,
    mkdir, unzip, is_zip_file, zip_contains_jar_entries, run, short_uid, timestamp,
    TIMESTAMP_FORMAT_MILLIS, md5, parse_chunked_data, now_utc, safe_requests,
    isoformat_milliseconds)
from localstack.utils.analytics import event_publisher
from localstack.utils.aws.aws_models import LambdaFunction
from localstack.utils.cloudwatch.cloudwatch_util import cloudwatched
APP_NAME = 'lambda_api'
PATH_ROOT = '/2015-03-31'
ARCHIVE_FILE_PATTERN = '%s/lambda.handler.*.jar' % config.TMP_FOLDER
LAMBDA_SCRIPT_PATTERN = '%s/lambda_script_*.py' % config.TMP_FOLDER
LAMBDA_RUNTIMES = [LAMBDA_RUNTIME_PYTHON27, LAMBDA_RUNTIME_PYTHON36,
    LAMBDA_RUNTIME_DOTNETCORE2, LAMBDA_RUNTIME_DOTNETCORE21, LAMBDA_RUNTIME_NODEJS,
    LAMBDA_RUNTIME_NODEJS610, LAMBDA_RUNTIME_NODEJS810, LAMBDA_RUNTIME_JAVA8,
    LAMBDA_RUNTIME_JAVA11, LAMBDA_RUNTIME_RUBY, LAMBDA_RUNTIME_RUBY25]
LAMBDA_DEFAULT_TIMEOUT = 3