feat(pagerduty): add scope config filters for incident collection

[csepulveda]

• I have read through the Contributing Documentation.
• I have added relevant tests.
• I have added relevant documentation.
• I will add labels to the PR, such as pr-type/bug-fix, pr-type/feature-development, etc.

Summary

This PR adds Priority and Urgency filtering capabilities to the PagerDuty plugin, allowing users to filter incidents during data collection based on their priority levels (P1-P5) and urgency (high/low).

Does this close any open issues?

Closes 8367

Screenshots

Other Information

This is my first PR to Devlake protect, please let me know if there is any extra documentation or test that need to be completed.

I test it using no filters and also using filter Priority=P1 and Urgency=High

[klesh]

Please change it to connections/:connectionId/scope-configs/:scopeConfigId/projects to comply RESTful convention.

[csepulveda]

Hello @klesh
I have a question, in other plugins: (bitbucket, github, gitlab, jira, trello, etc...) the path used is scope-config/:scopeConfigId/projects .

Let me know hoy to proceed.
Thanks for review this!.

[klesh]

Sorry, I missed the reply. It is scope-configs . please check https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/impl/impl.go#L319

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity for 120 days. It will be closed in 7 days if no further activity occurs.