duplicate limit functionality with paging+solution

Migrating may be tricky, so the earlier this is done the better. But it should be done with plenty of warning, i.e.:

• In an upcoming version of Wagn, make "paging" work just as "limit" does now. Deprecate the use of limit, letting people know that it will have a new meaning in a later version of Wagn. (this is duplicate limit functionality with paging)
• In the next (or some later) version of Wagn, change "limit" so that it specifies the total number of cards being returned. Do a migration that changes existing "limit" instuctions in WQL to "paging". Make sure the release notes mention this very prominently. (this is shift limit to mean total cards returned)