Remove invalid data from jira_tracker_data table

What does this MR do?

In !18639 (merged) we started migrating data for issue trackers and jira from properties field of services table to jira_tracker_data and issue_tracker_data. While everything went fine for issue_tracker_data the data were not properly migrated for jira_tracker_data. *_iv values are missing in some cases, mostly for api_url field.

While the final fix will be reinserting the data correctly, this MR removes the invalid data so that users can use their project.

Before reinserting the data we need to find the cause why it failed in the first place.

Records affected

gitlabhq_production=# select count(*) from jira_tracker_data WHERE (length(encrypted_api_url) > 0 AND encrypted_api_url_iv IS NULL) OR (length(encrypted_url) > 0 AND encrypted_url_iv IS NULL) OR (length(encrypted_username) > 0 AND encrypted_username_iv IS NULL) OR (length(encrypted_password) > 0 AND encrypted_password_iv IS NULL);
-[ RECORD 1 ]
count | 1953

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.

Issue: #198030 (closed)