Option to ignore locks, for secondary operations against environments

### Details

Thanks for the awesome action. npm already uses branch-deploy for deploying code changes and schema migrations.

We're looking at using branch-deploy to trigger data transitions (backfills) as well, which may need to run for days. We typically run `.lock --global` ahead of deploying code changes, but that blocks all executions of `github/branch-deploy`, regardless of `trigger`. I'm wondering if there's a way we can have code changes and transitions deploying independently.

Is there a way our transition workflow could ignore the global lock? Or could there be multiple types of locks, such that there's a global deployment lock, but also a global transition lock?

```yaml
- name: branch-deploy
uses: github/branch-deploy@10.0.0
with:
trigger: .transition
lock_type: transition
```

🤔 I see there's also a [`github/command` action](https://github.com/github/command) which likely ignores locks, but we'll need some way of referring to an environment.

首先检查 branch-deploy action 对全局锁、触发器值和环境引用的处理方式；将其与提到的 github/command action 进行比较。确定所请求的 workflow 应忽略全局锁，还是支持单独的锁类型，然后通过 action 现有的 workflow 配置和文档验证所选择的行为。

由索引模型根据 Issue 内容生成。