Utilize the dbFetchMaxRows on all requests, not just lookups

Maximo has the concept of a fetch stop limit (mxe.db.fetchResultStopLimit, set to 5000 by default) where users cannot traverse more than the number of records provided. IE as soon as you try to initialize MBO 5001, an error is thrown. But the actual query sent to the database server has no limit (such as select * from workorder order by schedstart). On platforms like SQL Server that do not utilize a server cursor (like Oracle does), this means the database server will read all the results (in this example, the entire table) to fulfill the request. On larger tables like WORKORDER, this leads to large waits on the database server.

Utilized out of the box for lookup dialogs primarily today, there is a feature in the MboSet code that you can utilize called setDBFetchMaxRows that will change the query executed to select top 5000 * from workorder order by schedstart if on SqlServer. Or in the case of Oracle, the where clause is modified to add rownum<=5000.

This request is to add a system property for when the fetch stop limit is set, that the stop limit is also set on the MboSet using setDBFetchMaxRows to avoid the database querying all the records they won't be utilized.

NOTE: There are existing features for adjusting the stop limit per object (so WORKORDER might be 25000 with the default limit of 5000 for other objects) or to ignore the fetch limit entirely for a set (either by calling setLogLargFetchResultDisabled(True) or by disabling the mxe.db.fetchStopLimitEnabled system property). The expectation in these scenarios is that the overridden limit is utilized or ignored entirely if the limit is disabled.