text: Title: OUTPUT_MAX_BYTES should be a setting
  Body: HNY!
  
  Just ran into the OUTPUT_MAX_BYTES warning, and it's quite a nuisance IMO.
  
  1) there's no recovering from this helpful message - not great, especially in App mode because it effectively breaks the page till the app is restarted
  2)  why does it `MARIMO_OUTPUT_MAX_BYTES` need to be an env var? it's not possible to change it without restarting everything - couldn't it be a setting? what's the idea of separating these rather random settings out into env vars?
  
  ```
  marimo supports the following environment variables for advanced configuration:
  
  | Environment Variable          | Description                                                                                                                  | Default Value   |
  | ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | --------------- |
  | `MARIMO_OUTPUT_MAX_BYTES`     | Maximum size of output that marimo will display. Outputs larger than this will be truncated.                                 | 5,000,000 (5MB) |
  | `MARIMO_STD_STREAM_MAX_BYTES` | Maximum size of standard stream (stdout/stderr) output that marimo will display. Outputs larger than this will be truncated. | 1,000,000 (1MB) |
  | `MARIMO_SKIP_UPDATE_CHECK`    | If set to "1", marimo will skip checking for updates when starting.                                                          | Not set         |
  
  ```
  
  3) OR could `mo._messaging.streams.OUTPUT_MAX_BYTES = 10_000_000` work similarly to `pd.options.display` (which can be changed  upfront in the notebook)?
  4)  I have indeed produced large output, but it might not have been considered that it is spread across many lazy tabs (altair charts)