[BUG] Alita fails with validation error when Jira issues lack the "priority" field during JQL search

[SamvelSimonyan]

Description
Some fields in Jira e.g. priority, are mandatory for the jira library used in sdk, In case jira does not have these fields, it will cause issues expecting the "priority" field to be present. We need to override it , to it will work with every jira configuration.

Precondition
E.g. "Priority" field is disabled in Jira

Steps to reproduce:

1. Create a jira toolkit ( cloud or server)
2. Use the "search_using_jql" tool to search for Jira issues in the project

   get CRM-48 using JQL
   
   

Actual results:

• Alita fails with a validation error when processing Jira issues that lack the "priority" field.

https://dev.elitea.ai/alita_ui/18/agents/all/167?viewMode=owner&name=Jira%20priority%20issue

Expected results:

• Alita should handle Jira issues with all possible field compositions, including cases where the "priority" field is missing.

Other info:

• This issue affects all projects where Jira issues lack the "priority" field.
• Root cause: Likely due to the Atlassian library used by Alita,

[SamvelSimonyan]

The agent was added @MikalaiB

[epamLDadayan]

@SamvelSimonyan please recreate the agent and reproduce it

[SamvelSimonyan]

Still reproducible https://dev.elitea.ai/alita_ui/18/agents/all/167?viewMode=owner&name=Jira%20priority%20issue

[epamLDadayan]

@nochore please have a look at this issue