chore(docs): Fix the documentation for TableProvider::scan()'s limit argument (#25397)

## Which issue does this PR close?

Closes N/A.

## Rationale for this change


https://docs.rs/datafusion/latest/datafusion/catalog/trait.TableProvider.html#limit
says
```
If limit is specified, the scan must produce at least this many rows, though it may return more
```

In SQL semantics the `LIMIT` tells the maximum number of rows to return.
Not the minimum.


## What changes are included in this PR?

Fixed the documentation for `TableProvider::scan()`'s `limit` argument
to match the similar documentation at
https://docs.rs/datafusion/latest/datafusion/catalog/struct.ScanArgs.html#method.with_limit

## What is the testing strategy for this PR?

Build the docs and verify that the documentation is correct.

## Are there any user-facing changes?

No.

Author: martin-g

datafusion/session/src/table.rs

@@ -150,8 +150,8 @@ pub trait TableProvider: Any + Debug + Sync + Send {
     ///
     /// # Limit
     ///
-    /// If `limit` is specified, the scan must produce *at least* this many
-    /// rows, though it may return more. Like Projection Pushdown and Filter
+    /// If `limit` is specified, the scan must produce *at most* this many
+    /// rows, though it may return less. Like Projection Pushdown and Filter
     /// Pushdown, DataFusion pushes `LIMIT`s as far down in the plan as
     /// possible. This is called "Limit Pushdown", and some sources can use the
     /// information to improve performance.