feat(jira): Allow filter jira board using devlake project name

[VaughanJ]

Please complete ALL items in this checklist, and remove before submitting

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

Summary

What does this PR do?
Add JIRA scope config support for filtering boards by the devlake project name

JIRA users can have large boards that track many components, the only solution at the moment is to have a board per deployable unit. but when you have 1000s of deployable units this needlessly explodes the number of JIRA boards needed.

Practical impact of these changes:

1. One Jira scope config can be reused across multiple DevLake projects.
2. Jira issue collection can automatically narrow results per project by matching Jira component to project name.
3. Reduces manual per-project board/filter setup for teams using shared Jira board configs.

Screenshots

Other Information

Question posted: #8955

[klesh]

I am not sure; it looks too inflexible to me. Why not allow users to specify an extra JQL condition?

[VaughanJ]

I was looking to find the lowest impact update, JQL per project would mean many 1000s of project level config scopes.

I will look to see if I can make the changes for JQL.