fix: percent-encode query string before signing to fix 401 with --fil…

…ter (#13)

When a query value contains special characters (e.g. a JSON filter like
{"ordStatus":"New"}), reqwest's url::Url::parse encodes them before
sending (" -> %22). The signature was computed over the raw unencoded
string, causing a server-side mismatch and a 401 Signature not valid.

Add signing_path() which parses the URL through the same url crate to
extract the canonically-encoded path+query, ensuring the signed string
matches what the server receives. Applied to get_auth and delete.

chore: bump version to v1.0.2, add Homebrew install instructions

feat: add default text annotations to order commands (#11)

Set 'Submitted via CLI.', 'Amended via CLI.', and 'Canceled via CLI.'
as defaults, matching BitMEX API convention. User-supplied --text still overrides.

Merge pull request #2 from BitMEX/feature/distribute

Distribution: CI, release pipeline, macOS signing & notarization

Bump version to 1.0.0-alpha.2

Co-Authored-By: Claude Sonnet 4.6 (1M context) <[email protected]>

Fix notarize step: extract binary from dist tarball

Co-Authored-By: Claude Sonnet 4.6 (1M context) <[email protected]>