chore(setup): replace LocalStack with moto-server for local SQS simulation

[prshant70]

Closes #26

What

Replaces LocalStack with the credential-free motoserver/moto Docker image as the local SQS simulator used by python3 notify_setup.py. The four superproject setup scripts (notify_setup.py, gateway_setup.py, core_setup.py, handler_setup.py) are updated: LocalStack install/start logic is removed, a moto-server container is started on port 5000 with a readiness poll, and all queue-creation commands previously using docker exec awslocal are replaced with direct boto3 calls against http://localhost:5000.

Why

LocalStack now requires authentication (a license token), which blocks first-time contributors from completing quick-setup with no AWS account. motoserver/moto is a drop-in replacement that requires no credentials, ships multi-arch Docker images (amd64 + arm64), and exposes a compatible HTTP endpoint on port 5000.

How

• notify_setup.py: deletes the LocalStack version-check/pip-install/start block; inserts docker rm --force moto-server, docker pull motoserver/moto, docker run -p 5000:5000 --detach --name moto-server, and a 30-retry stdlib urllib.request readiness poll. Updates the docker network connect call from localstack-main to moto-server. Adds import time and import urllib.request (stdlib only, no new dependencies).
• gateway_setup.py, core_setup.py, handler_setup.py: add import boto3; update darwin/linux SQS endpoint URL strings from port 4566 / localstack-main to port 5000 / moto-server; replace docker exec awslocal queue-creation subprocess loops with boto3.client('sqs', endpoint_url='http://localhost:5000', ...) loops using inline dummy credentials (non-secret moto-server placeholders). The queue-creation endpoint is unconditionally http://localhost:5000 on both macOS and Linux because the scripts run on the host and the container publishes port 5000 via -p 5000:5000. The SQS_ENDPOINT_URL values written to each service's config.json remain http://moto-server:5000 on Linux for container-to-container routing.

Testing

No automated test suite exists for these setup scripts. Manual verification:

# Clean run on macOS (Apple Silicon) or Linux — no AWS account required
python3 notify_setup.py

# Verify queues were created
python3 - <<'PYEOF'
import boto3
sqs = boto3.client('sqs', endpoint_url='http://localhost:5000',
                   region_name='us-east-1',
                   aws_access_key_id='test', aws_secret_access_key='test')
print(sqs.list_queues())
PYEOF

# Confirm no localstack or 4566 references remain
grep -r localstack notify_setup.py gateway_setup.py core_setup.py handler_setup.py
grep -r 4566 notify_setup.py gateway_setup.py core_setup.py handler_setup.py

# Syntax check
python3 -m py_compile notify_setup.py gateway_setup.py core_setup.py handler_setup.py

Passing state: notify_setup.py completes to ##### Congratulations! NotifyOne system setup Completed #####, list_queues returns all expected queue names, both grep commands return no output, py_compile exits 0. Re-running a second time must not fail with "container name already in use".

Checklist

• Tests pass (python3 -m py_compile notify_setup.py gateway_setup.py core_setup.py handler_setup.py)
• No secrets committed (dummy credentials test/test are non-secret moto-server placeholders)
• Manual verification: run python3 notify_setup.py on a clean machine with no AWS account and no LocalStack installed; confirm setup completes and list_queues returns expected queues; re-run a second time to confirm no "container name already in use" error

[deputydev-agent]

DeputyDev will no longer review pull requests automatically.To request a review, simply comment #review on your pull request—this will trigger an on-demand review whenever you need it.