Store Jira server type in `jira_tracking_data` table

What does this MR do?

We now query the Jira server and store the deployment type in the jira tracking data table. This is so we can make API decisions based on the type, Cloud or Server.

Since the API can create and update the jira service, we get query the Jira server in an after_commit callback. Otherwise we could maybe have relied on the test method which the UI calls.

Screenshots

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

Closes #229223 (closed)