Jira component: duplicate messages with the new issues consumer

When more than one JIRA issue fulfills the JQL and is available on a poll, it will result in duplicates handled multiple times in the next poll. It depends on how many issues were created within the poll delay. Issues will be handled N times (N is the number of issues that were created at the same time).

How to reproduce:

• Make sure to return multiple issues for a JQL query
• Wait multiple polls and review the resulting issues being handled by the Camel route