Adjust URL and account ID for proxying SQS requests to AWS

[whummer]

Fix URL and account ID for proxying SQS requests to AWS via the replicator/proxy extension. These changes were required for a recent demo given at an AWS Meetup: https://github.com/localstack/presentations/blob/main/2023-09-14_AWS-Community-Day-DACH/sample4/run.sh#L34

Had to temporarily disable part of the example app script, as the Lambda execution is currently failing with connection refused in CI (to be investigated):

[lambda e4cbf96395d8b7d8a94596f96de9ef7d] time="2023-09-16T22:12:04Z" level=panic msg="Post \"[http://172.17.0.2:443/_localstack_lambda/e4cbf96395d8b7d8a94596f96de9ef7d/status/e4cbf96395d8b7d8a94596f96de9ef7d/ready\](http://172.17.0.2:443/_localstack_lambda/e4cbf96395d8b7d8a94596f96de9ef7d/status/e4cbf96395d8b7d8a94596f96de9ef7d/ready/)": dial tcp 172.17.0.2:443: connect: connection refused" func=go.amzn.com/lambda/rapid.handleStart file="/home/runner/work/lambda-runtime-init/lambda-runtime-init/lambda/rapid/start.go:473"