If a query has multiple LIMIT clauses and one of them is in a subquery, the outer LIMIT is ignored.
For example, the below query returns 4 rows instead of 2:

select * from (
    select timestamp, symbol, venue,
           bids[1][1] as bid_price,
           bids[2][1] as bid_size,
           asks[1][1] as ask_price,
           asks[2][1] as ask_size
    from eq_equities_market_data
    where symbol='AAPL' and timestamp in '1970'
    limit -4
) limit 2;

This change fixes the problem.
It was tracked by the model if the limit has been implemented by a factory already.
It used a boolean, which did not allow for tracking multiple LIMIT clauses.
It is not the best choice to track this on the model anyway.
The LIMIT clause is represented by a node expression, which is copied to multiple places on the model tree.
It is better to track this on the node itself, and this way each LIMIT is tracked by the node which represents it in the model tree.

Also removed the followedLimitAdvice() method from RecordCursorFactory, it served the exact same purpose as implementsLimit().

required by https://github.com/questdb/questdb-enterprise/pull/828