feat(dogesec-cyberthreatexchange): add support for paginating via cursor on FEED/<id>/objects (#6668)

[fqrious]

Proposed changes

• Add support for new pagination type

Related issues

• closes fix(dogesec-cyberthreatexchange): add support for paginating via cursor on FEED/<id>/objects #6668

Checklist

• I consider the submitted work as finished
• I have signed my commits using GPG key.
• I tested the code for its functionality using different use cases
• I added/update the relevant documentation (either on github or on notion)
• Where necessary I refactored code to improve the overall quality

Further comments

[Filigran-Automation]

🤖 [AI-generated]

Hey @fqrious! 👋 I'm Sam, your convention guardian. Thanks a lot for the contribution! I reviewed PR #6664 and made a couple of small adjustments to align it with the repository conventions:

📝 Title

	Value
Before	add support for paginating via cursor on FEED/<id>/objects
After	feat(dogesec-cyberthreatexchange): add support for paginating via cursor on FEED/<id>/objects
Why	Titles follow Conventional Commits type(scope?)!?: description. This adds a new capability → feat:, with the connector directory name as the lowercase scope; FEED/<id>/objects preserved, no trailing period.

🏷️ Labels

Action	Label	Reason
✅ Added	community	A pull request must carry exactly one ownership label; as an external contribution this is community (LABELS.md §2/§6).

📋 PR Description Quality

Overall: Incomplete ❌

I haven't changed anything in your description — just flagging one thing to fix when you get a chance 🙏

Area	Problem	Suggestion
Related issues / title	"Related issues: N/A" — no linked issue, and the PR title is missing the required (#issue) reference.	CONTRIBUTING.md asks that every PR be linked to a GitHub issue describing the contribution. Please open a short issue and reference it both in Related issues (e.g. Closes #XXXX) and at the end of the PR title as … FEED/<id>/objects (#XXXX).

💡 For future PRs, please follow the contribution conventions and the title & label taxonomy.

Thanks for contributing! 🚀

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

❗ There is a different number of reports uploaded between BASE (17e5df1) and HEAD (aae6093). Click for more details.

HEAD has 110 uploads less than BASE

Flag	BASE (17e5df1)	HEAD (aae6093)
connectors	112	2

Additional details and impacted files

@@             Coverage Diff             @@
##           master    #6664       +/-   ##
===========================================
- Coverage   29.77%    0.34%   -29.44%     
===========================================
  Files        1933     1841       -92     
  Lines      120805   118197     -2608     
===========================================
- Hits        35964      402    -35562     
- Misses      84841   117795    +32954     

Files with missing lines	Coverage Δ
...mport/dogesec-cyberthreatexchange/src/connector.py	93.65% <100.00%> (+0.05%)	⬆️

... and 1037 files with indirect coverage changes

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.