[Salesforce] Add pagination support for login_rest and logout_rest data streams

[kush-elastic]

What does this PR do?

In the current Salesforce Integration, we don’t have pagination support for login-rest and logout-rest data streams. So if in any case, we have a response body with more than 2000 records, the next page is never called and the data will not be fetched.

Solution:
You can request the next batch of records using the provided URL with your instance and session information, and repeat until all records have been retrieved. These requests use nextRecordsUrl and don’t include any parameters. The final batch of records doesn’t have a nextRecordsUrl field and return true value for field done

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Related issues

• Relates Create package for Salesforce integration #3940
• Relates [salesforce] Add salesforce package foundation along with login_rest data stream #4261
• Relates [salesforce] Add salesforce package foundation along with logout_rest data stream #4323

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-12-19T12:43:42.684+0000

• Duration: 17 min 34 sec

Test stats 🧪

Test	Results
Failed	0
Passed	12
Skipped	0
Total	12

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (2/2)	💚
Files	100.0% (2/2)	💚 6.667
Classes	100.0% (2/2)	💚 6.667
Methods	100.0% (26/26)	💚 15.0
Lines	96.404% (429/445)	👍 0.382
Conditionals	100.0% (0/0)	💚

[agithomas]

Please complete the internal review. Send me a note once it is done

[harnish-crest-data]

Please complete the internal review. Send me a note once it is done

We are not able to provide approval from the Elastic account. It seems like still, some access is missing for the Elastic GitHub integration repo. Hence we are not able to approve. We have raised an IT ticket for the same.

[agithomas]

Please complete the internal review. Send me a note once it is done

We are not able to provide approval from the Elastic account. It seems like still, some access is missing for the Elastic GitHub integration repo. Hence we are not able to approve. We have raised an IT ticket for the same.

You may consider cancelling the IT ticket created for this purpose as it is not needed at the moment . If you decide to proceed, kindly ensure atleast one of the Elastic team member performs the code review.

cc @rameshelastic

[harnish-crest-data]

Please complete the internal review. Send me a note once it is done

We are not able to provide approval from the Elastic account. It seems like still, some access is missing for the Elastic GitHub integration repo. Hence we are not able to approve. We have raised an IT ticket for the same.

You may consider cancelling the IT ticket created for this purpose as it is not needed at the moment . If you decide to proceed, kindly ensure atleast one of the Elastic team member performs the code review.

cc @rameshelastic

Currently, only Kush has access, But when he raises the PR, others are not able to review it. So we need at least one more person who has the access to reviewers and approval.

[harnish-crest-data]

LGTM! Approved. ✅

[agithomas]

Approved

[elasticmachine]

Package salesforce - 0.2.1 containing this change is available at https://epr.elastic.co/search?package=salesforce