Handle limit pushdown in last cache

### Problem statement

The last cache does not handle limit pushdown:
https://github.com/influxdata/influxdb/blob/fa18b6d8da6c4e11ebbf5c042d4004cdab6acd63/influxdb3_cache/src/last_cache/table_function.rs#L76

### Proposed solution

Handle limit pushdown in the last cache. This was done in the distinct cache, so the solution _may_ be able to draw on the implementation there (see where limit is handled internally [here](https://github.com/influxdata/influxdb/blob/fa18b6d8da6c4e11ebbf5c042d4004cdab6acd63/influxdb3_cache/src/distinct_cache/cache.rs#L230)).

The `LastCacheExec`, should output the limit pushed down to the table function scan, as was done for the distinct cache.

### Additional context

See [slack thread](https://influxdata.slack.com/archives/C06BQA608J3/p1738705346635579).

Start in influxdb3_cache/src/last_cache/table_function.rs at the referenced limit-pushdown location, then compare the implementation in influxdb3_cache/src/distinct_cache/cache.rs around line 230. Trace LastCacheExec and confirm that the table function scan receives and outputs the pushed-down limit; done means last-cache scans handle limits like the distinct cache.

Written by the indexing model from the issue text.