[Feature] Publish the SJM CLI through Homebrew and Chocolatey #708

Publish the existing portable SJM CLI through the project-owned Homebrew tap and the Chocolatey Community repository.

This is deliberately a thin packaging layer:

• Homebrew downloads the checksum-pinned standalone tar, installs it under libexec, supplies Java 21, and exposes sjm on PATH.
• Chocolatey downloads the checksum-pinned standalone ZIP, exposes sjm on PATH, and stops the default daemon before upgrade or uninstall.
• Neither package starts a daemon or installs a service. Daemon use stays sjm send -d and sjm daemon ....

Package publication is an explicit post-release CircleCI action. A publish run checks out the release tag, requires a public final GitHub release, verifies the exact ZIP and tar names and hashes, checks that the tag, checkout, version, URLs, and package sources all agree, then parses and packs both package definitions before publishing anything. Rerunning after only one destination succeeded is safe.

For 10.0.0, run the package smoke workflow once before publication:

• On macOS, install from a local tap, confirm installation did not start a daemon, run sjm daemon --help, and uninstall.
• On Windows, install a local 10.0.0-test1, confirm installation did not start a daemon, start the default daemon, upgrade to local 10.0.0, verify the new command, and uninstall.

Repeat those smoke checks only when the package templates or installation behavior materially change. Normal releases can use the publish action directly after their GitHub release assets are public.

Keep this issue open until brew install simple-java-mail/tap/sjm works and Chocolatey has approved and listed sjm 10.0.0. After both are public, add those commands to the website without removing the standalone ZIP and tar route.