Prioritize narrower reference matches over broader matches in Jira Plugin

When multiple CoffeeCup projects are associated with a Jira project or a Jira Label, and the Jira plugin is opened on an issue page, the Plugin selects the first eligible match from the list of projects, rather than prioritizing the matches based on their specificity.

The expectation from a user perspective is that the more specific matches, like the label matching method, should be prioritized above the project-level matching or entire Jira instance matching.

Expected order for Jira matching:

• Label

• Epic

• Project

• Workspace

Expected order for non-Jira matching

• Scope / Project (if applicable)

• Workspace