fix: add e2e/smoke to tar so bcr presubmit can run (#20)

### TL;DR

Add a smoke test for rules_formatjs and include it in release artifacts.

### What changed?

- Created a new smoke test in `e2e/smoke/` directory with a minimal setup to verify FormatJS CLI functionality
- Updated BCR presubmit configuration to use the new smoke test instead of the previous example
- Enhanced the release preparation script to include the smoke test in release artifacts
- Added testing instructions to the release notes

### How to test?

Run the smoke test with:
```bash
cd e2e/smoke
bazel build //:extract
```

This will extract messages from a simple React component and verify that the FormatJS CLI toolchain is working correctly.

### Why make this change?

This change provides users with a simple way to verify that rules_formatjs works in their environment without needing to set up a complex example. Including the smoke test in the release artifact makes it easier for users to test the rules immediately after installation, improving the user experience and reducing potential setup issues.

Author: longlho

.bcr/presubmit.yml

@@ -1,5 +1,5 @@
 bcr_test_module:
-  module_path: "examples/simple"
+  module_path: "e2e/smoke"
   matrix:
     platform: ["debian10", "macos", "ubuntu2004"]
     bazel: ["8.x"]

.github/workflows/release_prep.sh

@@ -12,7 +12,21 @@ PREFIX="rules_formatjs-${TAG:1}"
 ARCHIVE="rules_formatjs-$TAG.tar.gz"
 
 # NB: configuration for 'git archive' is in /.gitattributes
-git archive --format=tar --prefix=${PREFIX}/ ${TAG} | gzip > $ARCHIVE
+# Create the main archive
+git archive --format=tar --prefix=${PREFIX}/ ${TAG} > "${ARCHIVE%.gz}"
+
+# Add e2e/smoke test to the archive (examples are excluded by .gitattributes but we want smoke test included)
+# Create a temporary directory with the smoke test in the right structure
+TMPDIR=$(mktemp -d)
+mkdir -p "${TMPDIR}/${PREFIX}/e2e"
+# Copy smoke test but exclude bazel output directories and lock files
+rsync -a --exclude='bazel-*' --exclude='MODULE.bazel.lock' e2e/smoke/ "${TMPDIR}/${PREFIX}/e2e/smoke/"
+tar -rf "${ARCHIVE%.gz}" -C "${TMPDIR}" .
+rm -rf "${TMPDIR}"
+
+# Compress the archive
+gzip "${ARCHIVE%.gz}"
+
 SHA=$(shasum -a 256 $ARCHIVE | awk '{print $1}')
 
 # Add generated API docs to the release, see https://github.com/bazelbuild/bazel-central-registry/issues/5593
@@ -34,4 +48,15 @@ bazel_dep(name = "rules_formatjs", version = "${TAG:1}")
 \`\`\`
 
 That's it! The toolchains are automatically registered.
+
+## Testing the Installation
+
+A smoke test is included in the release at \`e2e/smoke/\`. To verify the rules work in your environment:
+
+\`\`\`bash
+cd e2e/smoke
+bazel build //:extract
+\`\`\`
+
+This will extract messages from a simple React component and verify that the FormatJS CLI toolchain is working correctly.
 EOF

e2e/smoke/.bazelrc

@@ -0,0 +1,2 @@
+# Minimal bazelrc for smoke test
+common --enable_bzlmod

e2e/smoke/BUILD.bazel

@@ -0,0 +1,8 @@
+load("@rules_formatjs//formatjs:defs.bzl", "formatjs_extract")
+
+# Extract messages from source files
+formatjs_extract(
+    name = "extract",
+    srcs = ["src/Hello.tsx"],
+    out = "messages.json",
+)

e2e/smoke/MODULE.bazel

@@ -0,0 +1,12 @@
+"""Smoke test for rules_formatjs - minimal test to verify basic functionality"""
+
+module(
+    name = "smoke_test",
+    version = "0.0.0",
+)
+
+bazel_dep(name = "rules_formatjs", version = "0.0.0")
+local_path_override(
+    module_name = "rules_formatjs",
+    path = "../..",
+)

e2e/smoke/MODULE.bazel.lock

@@ -0,0 +1,37 @@
+# Smoke Test
+
+This is a minimal end-to-end test that verifies basic functionality of `rules_formatjs`.
+
+## Purpose
+
+This smoke test is included in the release artifact to allow users to quickly verify that the rules work in their environment without needing to set up a complex example.
+
+## What it tests
+
+- Basic message extraction from a React component using `formatjs_extract`
+- FormatJS CLI toolchain selection and execution
+- Module extension setup and toolchain registration
+
+## Running the test
+
+From this directory:
+
+```bash
+bazel build //:extract
+```
+
+This should successfully extract messages from `src/Hello.tsx` and produce a `messages.json` file with the extracted internationalization messages.
+
+## Expected output
+
+The build should succeed and produce `bazel-bin/messages.json` containing:
+
+```json
+{
+  "hello.world": {
+    "id": "hello.world",
+    "defaultMessage": "Hello, World!",
+    "description": "Simple greeting message"
+  }
+}
+```

e2e/smoke/README.md

@@ -0,0 +1 @@
+# Marker file for Bazel workspace

e2e/smoke/REPO.bazel

@@ -0,0 +1,13 @@
+import { FormattedMessage } from "react-intl";
+
+export function Hello() {
+  return (
+    <div>
+      <FormattedMessage
+        id="hello.world"
+        defaultMessage="Hello, World!"
+        description="Simple greeting message"
+      />
+    </div>
+  );
+}