chore: claude code permissions should not be checked in (#2269)

The permissions file allows all `bash` commands (`Bash(*)`), but even if
it didn't it still allows many dangerous commands (`Bash(rm:*)`,
`Bash(node:*)`).

While I don't think this in and of itself is really all that
exploitable, I do think it increases the exposure risk of community
members.

People who want to contribute to the repository may become at risk to
something like a compromised MCP server or a model going a bit wild,
even if they would normally manually approve commands.

My personal take is that a public repository should not prescribe
permissions for something as powerful as Claude Code.

[Anthropic's
documentation](https://docs.anthropic.com/en/docs/claude-code/settings#settings-files)
suggest adding `.claude/settings.local.json` to the `.gitignore`, as
well.

<!-- ELLIPSIS_HIDDEN -->

----

> [!IMPORTANT]
> Remove all allowed Bash commands from `.claude/settings.local.json` to
reduce exposure risk.
> 
>   - **Permissions**:
> - Remove all allowed Bash commands from `permissions` in
`.claude/settings.local.json`, leaving `allow` list empty.
>     - No changes to `deny` list.
> 
> <sup>This description was created by </sup>[<img alt="Ellipsis"
src="https://img.shields.io/badge/Ellipsis-blue?color=175173">](https://www.ellipsis.dev?ref=BoundaryML%2Fbaml&utm_source=github&utm_medium=referral)<sup>
for e6cc466. You can
[customize](https://app.ellipsis.dev/BoundaryML/settings/summaries) this
summary. It will automatically update as commits are pushed.</sup>

<!-- ELLIPSIS_HIDDEN -->

---------

Co-authored-by: Sam Lijin <sam@boundaryml.com>

Author: ActuallyTrent

.claude/settings.local.json

@@ -167,6 +167,7 @@ jj-workflow.mdc
 # mise
 .mise.local.toml
 .mise.*.local.toml
+.claude/settings.local.json
 third_party
 
 baml_repl_history.txt