doc: Add docs for negative inbound filters (#5336)

Co-authored-by: Isabel <[email protected]>

Author: untitaker

src/docs/product/data-management-settings/filtering/index.mdx

@@ -60,7 +60,7 @@ To ensure you’re adding the correct message to the inbound filter setting, che
 To filter releases, keep the following in mind:
 
 - The filter matches the full release name provided during SDK initialization. If you provide the recommended package prefix, the release is in the format `package@version`, for example: `[email protected]`.
-- Regular glob rules apply and there is no special casing for SemVer. This allows for matching prefixes, such as `my-example@1.*`.
+- Globbing rules apply and there is no special casing for SemVer. This allows for matching prefixes, such as `my-example@1.*`.
 - The filter never applies to events without a release.
 
 ### Glob Matching
@@ -73,3 +73,13 @@ Some symbols, such as the `*` character, receive special meaning as meta charact
 - `*` matches zero or more characters.
 - `\` escapes the next character making it literal. If it precedes a non-meta character, the backslash is ignored.
 - `[`, `]`, `{`, and `}` are reserved meta characters.
+- `!` works for negation, but only within brackets, such as in `[!1-4]` to match any character that is not `[1-4]`.
+
+Generally, `bash`'s out-of-the-box behavior for globbing is close to what Sentry supports:
+
+```bash
+touch 1.2.3
+touch 1.2.4
+echo 1.2.*
+echo 1.2.[!3]
+```