TDL-19486 Add limit clause to core stream queries

[prijendev]

Description of change

• Added support of configurable page limit parameter into the tap.
• LIMIT parameter is added for all core streams except the below streams,
  • call_details
  • campaign_lables
  • ad_group_criterion
  • campaign_criterion
• LIMIT clauses in the ad_group_criterion and campaign_criterion(stream which has composite primary keys) may result in the infinite loop.
  • For example, the limit is 10. campaign_criterion stream has a total of 20 records with campaign_id = 1 . So, in the first call, the tap retrieves 10 records, and the next time query would look like the below,
    WHERE campaign_id >= 1
  • Now, the tap will again fetch records with campaign_id = 1. That's why we should not pass the LIMIT clause in the query of these streams.
  • We can not do queries like WHERE pk_1 > 1 OR (pk_1 = 1 and pk_2 > 1) because google ads do not support OR parameter. We had a slack conversation about the same.
• Added unit test case to validate different values of the query_limit parameter
• Added integration test case.

QA steps

• automated tests passing
• manual qa steps passing

Risks

• Dependent on this connections-service migration because testing expects a configurable query_limit to be accepted in config

Rollback steps

• revert this branch

[kspeer825]

These are good test cases.