Return only supported issue types for selected Jira Project

What does this MR do?

Related to #276892 (closed)

This change improves the way we fetch available issue types for Jira. From now we will fetch only these types that are available in the workflow for given project instead of loading all possible issue types from the system.

Unfortunately jira-ruby gem is not supporting resources we want to fetch, that is why we are reusing some parts of the gem to load it using our custom logic.

We are using:

1. Get issue type schemes for projects to list all type schemes for selected project in JIRA
2. Get issue type scheme items to fetch list of issue type IDs that are supported in selected issue type schemes from previous point.
3. Filter issue types with IDs from previous point.

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team