Broken reading localstack localdb because trying to read backups that do not exist

[ktwbc]

Describe the bug
When using localstack (https://localstack.cloud) which includes local dynamodb within it, we can run a local dynamo instance on endpoint http://localhost:4566
When the plugin reads the local info, I see in the docker logs it's attempting two reads:

A ListTables followed by a ListBackups. The ListBackups fails with 400 because it's not supported, and that's causing the tables it found not to be displayed.

2025-04-05T17:22:50.612 INFO --- [et.reactor-0] localstack.request.aws : AWS dynamodb.ListTables => 200
2025-04-05T17:22:50.624535264Z 2025-04-05T17:22:50.624 INFO --- [et.reactor-0] localstack.request.aws : AWS dynamodb.ListBackups => 400

Steps to reproduce

1. Install LocalStack by using docker:

docker run -d \
  --name localstack   \
  -p 4566:4566 -p 4510-4559:4510-4559 \
  -e SERVICES=dynamodb\
  -e DOCKER_HOST=unix:///var/run/docker.sock \
  localstack/localstack

2. set up plugin to use DynamoDB Local, endpoint http://localhost:4566
3. Create a table via plugin say from a copy action from another ddb database
4. Hit reload (refresh) on plugin to re-read database, table will be missing

Expected behavior
Should read tables

I can confirm with awslocal that it's running and I have tables

awslocal dynamodb list-tables
{
    "TableNames": [
        "local-active-users",

Environment information:

• OS: MacOS
• IDE version: Webstorm latest
• plugin version: 2024.1.1-243

[ktwbc]

ok I figured out what was going on. My actual AWS account uses us-east-2. When I set up localstack, it used that from my profile to set up my "fake" aws env in that container, so that's where my data was going. I see in a localstack's persisted folder that the us-east-2 ddb file was obviously where my data was. The plugin here goes to us-east-1 and I didn't notice the advanced/custom endpoint, where I could put in us-east-2 there. When I changed to that, my tables showed up in the plugin.