Improve the way we generate links between Jira issues and build results

Summary

Right now Bamboo stores the Jira issue key associated to a build result in the BRS_LINKEDJIRAISSUES table. The problem is with the way we store the information. Bamboo does not keep the entire URL to the Jira instance where the link was originally pointing to (e.g. http://localhost:8080/browse/TEST-1), only the Jira issue key (e.g. TEST-1). Therefore, if you have multiple Jira instances connected to Bamboo and the prefix of a Jira issue exists in more than one Jira instance, Bamboo will always assume that the Jira issue is coming from the 'primary' application link or in case there's no Jira issue with that prefix in the 'primary' application, the first Jira application that has a matching prefix, following top to bottom in the list of application links.

Expected Results

We should improve the way we store this information so that when we first create a link between a Jira issue and a build result, the entire URL to the Jira issue is stored (e.g. http://localhost:8080/browse/TEST-1 instead of just TEST-1) to avoid confusion and preserve the original association.