docs(oss): the notify example must use gh api -f, not -F (#269)

`docs/oss/release-automation.md` shows product repositories how to send
the `product-published` dispatch with `gh api ... -F
'client_payload[package]=@prisma/composer-cli'`. `-F` reads a value that
starts with `@` from a file, so that line fails with `open
prisma/composer-cli: no such file or directory` before any request is
made. prisma/composer#295 copied the example verbatim and its review bot
caught it. `-f` sends the literal string.

Two characters changed; no code.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

Author: wmadden-electric

docs/oss/release-automation.md

@@ -56,8 +56,8 @@ A step in the publish workflow, immediately after its publish step and keyed on
   run: |
     gh api repos/prisma/prisma-cli/dispatches \
       -f event_type=product-published \
-      -F 'client_payload[package]=@prisma/composer-cli' \
-      -F "client_payload[version]=$VERSION"
+      -f 'client_payload[package]=@prisma/composer-cli' \
+      -f "client_payload[version]=$VERSION"
 ```
 
 The payload is informational — this repository always re-reads the registry rather than trusting the event, so a malformed or replayed event cannot pin a version that does not exist.