feat: limit bundle by data size

[segfault-magnet]

Closes: #157

Bundling can now be configured by two new config parameters:

- **`COMMITTER__APP__BUNDLE__MAX_FRAGMENTS_PER_BUNDLE`**

  - **Description:** Maximum number of fragments allowed per bundle. This limits the size of any individual bundle.
  - **Type:** Positive integer (`NonZeroUsize`)
  - **Example:** `10`
  
  - **`COMMITTER__APP__BUNDLE__BYTES_TO_ACCUMULATE`**

  - **Description:** Byte threshold that, if reached before the accumulation timeout expires, will trigger bundling immediately.
  - **Format:** Human-readable byte string (e.g., `10MB`, `500KB`)
  - **Example:** `1MB`

The idea is that we can configure the committer to give lots of data for the bundler to work with (ie achieve better compression, gas usage) while allowing it to only generate bundles that fit in N eth blobs.

Along with that we also bundle if we accumulate the configured number of blocks, so that we are more lively when we have a large backlog of unbundled blocks that are small, for example.

And there is the traditional timeout that will bundle anyways if we haven't bundled anything for a long time.

Also grouped together blocks before importing them. Mainly to avoid an edgecase mentioned in the bundler code but also to reduce the number of "imported N..=N+1 logs" we had.

[hal3e]

Nicely done. Left some small comments. In addition to the original task, thanks for the docs update and adding chunked fuel block imports.

[digorithm]

LGTM. Great work on this, looking forward to seeing it live!