fix: vtable max rows limit not applied

Summarize the changes

• fix: vtable max rows limit not applied

• We didn't apply vtable max rows value when executing local sql. We tried to lookup it in the execute options hashmap and took the default value instead, though it was not stored in the hashmap.

Ensure that

• New code is covered by unit and integration tests.
• Related issues would be automatically closed with gitlab's closing pattern (Closes #issue_number).
• Public modules are documented (check the rendered version with cargo doc --open).
• (if PEST grammar has changed) EBNF grammar reflects these changes (check the result with railroad diagram generator.

close #845 (closed)

Next steps

• Cherry-pick to: none
• Update sbroad submodule in picodata/picodata.
• (if EBNF grammar has changed) create a follow-up issue in picodata/docs.