DOC-339: Address hovaesco's technical review round

- Add the docker socket mount to both the Docker Compose and Docker
  CLI examples, confirmed needed same as AWS (hovaesco).
- Remove the redundant "Update lstk" step right after a fresh
  install (hovaesco).
- Rename the Docker Compose service key to localstack-snowflake for
  clarity, and update the "View logs" Docker Compose command to
  match (hovaesco/Maureen).
- Add --name localstack-snowflake to the Docker CLI start command:
  the "docker logs -f localstack-snowflake" example didn't work
  without it, since no --name was set (hovaesco).
- Fix the auth-token guide's lingering `lstk start --type snowflake`
  to plain `lstk start`, consistent with the installation guide.
- Use distinguishable, realistic-looking test credentials in Local
  Development now that hovaesco confirmed the Python emulator has no
  format limitation there (Maureen's original suggestion).
- Migrate the remaining two tutorials (aws-lambda-localstack-snowpark
  and s3-tables-iceberg-integration) from the legacy `localstack` CLI
  to lstk, matching the credit-scoring tutorial fixed earlier and
  answering hovaesco's "why only one of three" question.

Author: quetzalliwrites

src/content/docs/snowflake/getting-started/auth-token.mdx

@@ -55,7 +55,7 @@ Authentication requirements vary based on your chosen execution method.
 The `lstk` CLI automates the authentication lifecycle. On initial execution, it triggers a browser-based OAuth flow and stores the resulting token in your system keyring. No manual environment variable configuration is required.
 
 ```bash
-lstk start --type snowflake
+lstk start
 ```
 
 You can alternatively set the `LOCALSTACK_AUTH_TOKEN` environment variable in your shell session; `lstk` uses it when no keyring token is present. See [Authentication](/aws/developer-tools/running-localstack/lstk/#authentication) for the full resolution order.

src/content/docs/snowflake/getting-started/installation.mdx

@@ -61,12 +61,6 @@ type = "snowflake"
 port = "4566"
 ```
 
-### Update lstk
-
-```bash
-lstk update
-```
-
 For more details, see the [lstk documentation](/aws/developer-tools/running-localstack/lstk/).
 
 ## Container and orchestration tools
@@ -81,7 +75,7 @@ Create a `docker-compose.yml` with the following configuration:
 
 ```yaml showLineNumbers
 services:
-  localstack:
+  localstack-snowflake:
     container_name: '${LOCALSTACK_DOCKER_NAME:-localstack-snowflake}'
     image: localstack/snowflake
     ports:
@@ -95,6 +89,7 @@ services:
       - PERSISTENCE=${PERSISTENCE:-0}
     volumes:
       - '${LOCALSTACK_VOLUME_DIR:-./volume}:/var/lib/localstack'
+      - '/var/run/docker.sock:/var/run/docker.sock'
 ```
 
 Execute `docker compose up` to start.
@@ -106,10 +101,12 @@ Use the Docker CLI for one-off starts or when you want to test a container confi
 ```bash
 docker run \
   --rm -it \
+  --name localstack-snowflake \
   -p 127.0.0.1:4566:4566 \
   -p 127.0.0.1:4510-4559:4510-4559 \
   -p 127.0.0.1:443:443 \
   -e LOCALSTACK_AUTH_TOKEN=${LOCALSTACK_AUTH_TOKEN:?} \
+  -v /var/run/docker.sock:/var/run/docker.sock \
   localstack/snowflake
 ```
 
@@ -167,7 +164,7 @@ For `lstk` CLI diagnostics (separate from container logs), see [Logging](/aws/de
 <TabItem label="Docker Compose">
 
 ```bash
-docker compose logs -f localstack
+docker compose logs -f localstack-snowflake
 ```
 
 </TabItem>

src/content/docs/snowflake/getting-started/local-development.mdx

@@ -41,9 +41,9 @@ Create a connection profile that points the Snowflake CLI at your local emulator
 ```bash
 snow connection add \
     --connection-name localstack \
-    --user test \
-    --password test \
-    --account test \
+    --user test_user \
+    --password TestPassword1! \
+    --account test-account \
     --host snowflake.localhost.localstack.cloud
 ```
 
@@ -64,8 +64,8 @@ snow connection test --connection localstack
 | Connection name | localstack                           |
 | Status          | OK                                   |
 | Host            | snowflake.localhost.localstack.cloud |
-| Account         | test                                 |
-| User            | test                                 |
+| Account         | test-account                         |
+| User            | test_user                            |
 +--------------------------------------------------------+
 ```
 

src/content/docs/snowflake/tutorials/aws-lambda-localstack-snowpark.md

@@ -19,7 +19,7 @@ The code in this tutorial is available on [GitHub](https://github.com/localstack
 
 ## Prerequisites
 
-- [`localstack` CLI](/snowflake/getting-started/installation/) with a [`LOCALSTACK_AUTH_TOKEN`](/snowflake/getting-started/auth-token/)
+- [`lstk`](/snowflake/getting-started/installation/) with a [`LOCALSTACK_AUTH_TOKEN`](/snowflake/getting-started/auth-token/)
 - [LocalStack for Snowflake](/snowflake/getting-started/)
 - [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) & [`awslocal` wrapper](/aws/connecting/aws-cli/#localstack-aws-cli-awslocal)
 - Python 3.10 installed locally
@@ -141,12 +141,12 @@ Start your LocalStack container in your preferred terminal/shell.
 
 ```bash showLineNumbers
 export LOCALSTACK_AUTH_TOKEN=<your_auth_token>
-DEBUG=1 \
-LAMBDA_RUNTIME_ENVIRONMENT_TIMEOUT=180 \
-localstack start --stack snowflake
+LOCALSTACK_DEBUG=1 \
+LOCALSTACK_LAMBDA_RUNTIME_ENVIRONMENT_TIMEOUT=180 \
+lstk start --type snowflake
 ```
 
-> The `DEBUG=1` environment variable is set to enable debug logs. It would allow you to see the SQL queries executed by the Lambda function. The `LAMBDA_RUNTIME_ENVIRONMENT_TIMEOUT` environment variable is set to increase the Lambda function's timeout to 180 seconds.
+> The `LOCALSTACK_DEBUG=1` environment variable is set to enable debug logs. It would allow you to see the SQL queries executed by the Lambda function. The `LOCALSTACK_LAMBDA_RUNTIME_ENVIRONMENT_TIMEOUT` environment variable is set to increase the Lambda function's timeout to 180 seconds.
 
 ## Deploy the Lambda function
 
@@ -170,7 +170,7 @@ awslocal lambda invoke --function-name localstack-snowflake-lambda-example \
 	--payload '{"body": "test"}' output.txt
 ```
 
-You will receive a response with the details of the invocation. You can view the output in the `output.txt` file. To see the SQL queries executed by the Lambda function, check the logs by navigating to LocalStack logs (`localstack logs`).
+You will receive a response with the details of the invocation. You can view the output in the `output.txt` file. To see the SQL queries executed by the Lambda function, check the logs by navigating to LocalStack logs (`lstk logs`).
 
 ```bash
 2024-02-07T17:33:36.763 DEBUG --- [   asgi_gw_3] l.s.l.i.version_manager    : [localstack-snowflake-lambda-example-b0813b21-ad5f-4ec7-8fb4-53147df9695e] Total # of rows: 3

src/content/docs/snowflake/tutorials/s3-tables-iceberg-integration.md

@@ -18,7 +18,7 @@ With LocalStack's Snowflake emulator, you can create catalog integrations that c
 
 ## Prerequisites
 
-- [`localstack` CLI](/snowflake/getting-started/installation/) with a [`LOCALSTACK_AUTH_TOKEN`](/snowflake/getting-started/auth-token/)
+- [`lstk`](/snowflake/getting-started/installation/) with a [`LOCALSTACK_AUTH_TOKEN`](/snowflake/getting-started/auth-token/)
 - [LocalStack for Snowflake](/snowflake/getting-started/)
 - [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/install-cliv2.html) & [`awslocal` wrapper](/aws/connecting/aws-cli/#localstack-aws-cli-awslocal)
 - Python 3.10+ with `pyiceberg` and `pyarrow` installed
@@ -29,7 +29,7 @@ Start your LocalStack container with the Snowflake emulator enabled.
 
 ```bash
 export LOCALSTACK_AUTH_TOKEN=<your_auth_token>
-localstack start --stack snowflake
+lstk start --type snowflake
 ```
 
 ## Create S3 Tables resources