Issue Summary:

Jira Macro Repair doesn't update macros if it's not able to find the application ID entry in the bandana table. It will log a message similar to

WARN	Couldn't find type id for application link with ID 170e1c03-4c2e-322b-8eab-b7deb241f722. Link is corrupted

In most cases we see an entry similar to the one below from this SQL query

SELECT * FROM bandana where bandanavalue ilike '%applinks%';

2064389,	_GLOBAL,	applinks.global.application.ids,	<list><string>170e1c03-4c2e-322b-8eab-b7deb241f722</string></list>

This would match what's returned by https://<host>.atlassian.net/wiki/rest/applinks/latest/applicationlink

Steps to Reproduce:

1. Configure an applink in the cloud tenant using the TCS record, or use the existing System Link
2. Delete the application link entry from the cloud bandana table
3. It should still be available from the UI at [/wiki/rest/applinks/latest/applicationlink]
4. Create a page with Jira macros in the confluence server
5. perform a migration to Confluence Cloud
6. Run Jira macro repair

Expected Results

Jira Macro Repair execution fixes the broken Jira macros.

Actual Results

Jira Macro Repair doesn't fix the broken macros and instead returns a 'Link is corrupted' message.

According to this page, the bandana entry may not be there and isn't needed
https://hello.atlassian.net/wiki/spaces/CAXP/pages/2743279792/Application+Links+for+Confluence+Cloud+-+Quick+Facts#I-can%E2%80%99t-find-data-for-system-applink-in-the-database

- Sometimes you will find system applink data in the database (usually because the customer has connected a direct link as well), however Confluence DOES NOT need this
- Confluence can configure an applink just through using the TCS record
- Therefore you can expect sometimes to not see a system applink in bandana

 We can confirm JMR checks the bandana table by modifying the applink entry, instead of deleting it, and running JMR after a migration. In that case, we see following log entries

ctx.tenantId: f3341c18-2733-4292-aaea-305597ef7ba5	
ext.traceId: 004275a27d0f311b

WARN	Couldn't find type id for application link with ID ffff1111-4c2e-322b-8eab-b7deb241f722. Link is corrupted	

Workaround

Contact Atlassian Support.