chore: release v4.7.3 (#4997)

## Summary
1 new feature, 6 improvements, 4 bug fixes.

## Breaking changes
- Creating or resuming a session with `POST /api/v1/sessions` now
requires both session-write and task-trigger permissions. Scoped keys
and public tokens must grant `write:sessions` (or access to the target
session) and permission to trigger its task.

## Improvements
- Update the minimatch dependency to ^10.2.3.
([`5236799b7`](5236799))
- Add `trigger.dev orgs list` to show the organizations you belong to,
with their slugs and IDs. Use the slug with `trigger.dev projects create
--org`, including for organizations that don't have any projects yet.
`trigger.dev projects create` now activates the Free plan for
organizations that don't have a plan yet, matching `trigger.dev init`.
([`68ee6be4b`](68ee6be))
- Reports filed with the `submit_feedback` MCP tool now reach the
Trigger.dev team. They were being sent, but not somewhere anyone was
reading.
([`4a94982a1`](4a94982))
- Stopping a `chat.agent` turn whose `run()` returns a `streamText`
result no longer sends an `error` chunk with "An unexpected error
occurred". The turn ends quietly again and the run stays alive for the
next message.
([`64c3ba13c`](64c3ba1))
- `chat.createStartSessionAction`, `chat.headStart` and
`chat.startHeadStart` now accept `tags` for the Session itself, so chat
sessions can be filtered by tag on the Sessions page.
`triggerConfig.tags` still tags the session's runs.
([`9dbc5f984`](9dbc5f9))
  
  ```ts
  await startChatSession({
  chatId,
  clientData,
  tags: [`org:${org.slug}`, `user:${user.id}`],
  });
  ```

## Server changes

These changes affect the self-hosted Docker image and Trigger.dev Cloud:

- Self-hosted instances can block sign-in and sign-up from specific
email domains with the new `BLOCKED_EMAIL_DOMAINS` setting.
- Run traces now appear almost immediately and load progressively as you
watch, and much larger traces are viewable than before.
- The Logs page loads and searches faster, and busy environments no
longer fail to load it. Searches that are still too expensive now show a
message suggesting a narrower range instead of a generic error.
- Fix a rare case where a run could stay stuck executing after the child
run or wait it was waiting on had completed.
- Deployments with an unsupported `runtime` now fail with a 400 that
names the supported runtimes, instead of a generic 500
- Preserve the cancellation reason when a run that was executing is
finalized, instead of replacing it with the default text.

<details>
<summary>Raw changeset output</summary>

# Releases
## @trigger.dev/build@4.7.3

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.7.3`
## trigger.dev@4.7.3

### Patch Changes

- Update the minimatch dependency to ^10.2.3.
([`5236799b7`](5236799))
- Add `trigger.dev orgs list` to show the organizations you belong to,
with their slugs and IDs. Use the slug with `trigger.dev projects create
--org`, including for organizations that don't have any projects yet.
`trigger.dev projects create` now activates the Free plan for
organizations that don't have a plan yet, matching `trigger.dev init`.
([`68ee6be4b`](68ee6be))
- Reports filed with the `submit_feedback` MCP tool now reach the
Trigger.dev team. They were being sent, but not somewhere anyone was
reading.
([`4a94982a1`](4a94982))
- Updated dependencies:
  - `@trigger.dev/build@4.7.3`
  - `@trigger.dev/core@4.7.3`
  - `@trigger.dev/schema-to-json@4.7.3`
## @trigger.dev/python@4.7.3

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/sdk@4.7.3`
  - `@trigger.dev/build@4.7.3`
  - `@trigger.dev/core@4.7.3`
## @trigger.dev/react-hooks@4.7.3

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.7.3`
## @trigger.dev/redis-worker@4.7.3

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.7.3`
## @trigger.dev/rsc@4.7.3

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.7.3`
## @trigger.dev/schema-to-json@4.7.3

### Patch Changes

- Updated dependencies:
  - `@trigger.dev/core@4.7.3`
## @trigger.dev/sdk@4.7.3

### Patch Changes

- Stopping a `chat.agent` turn whose `run()` returns a `streamText`
result no longer sends an `error` chunk with "An unexpected error
occurred". The turn ends quietly again and the run stays alive for the
next message.
([`64c3ba13c`](64c3ba1))
- `chat.createStartSessionAction`, `chat.headStart` and
`chat.startHeadStart` now accept `tags` for the Session itself, so chat
sessions can be filtered by tag on the Sessions page.
`triggerConfig.tags` still tags the session's runs.
([`9dbc5f984`](9dbc5f9))

  ```ts
  await startChatSession({
    chatId,
    clientData,
    tags: [`org:${org.slug}`, `user:${user.id}`],
  });
  ```

- Updated dependencies:
  - `@trigger.dev/core@4.7.3`
## @trigger.dev/core@4.7.3

</details>

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: github-actions[bot]