OAUTHCONSUMER.consumername is not updated to System application title

Summary

When configuring an application link, JIRA provides the value of the OAUTHCONSUMER table's consumername column to the remote application. This value is subsequently used in security dialogs, e.g. "Your Company JIRA would like read/write access to Bitbucket".

However, the value here is not configurable anywhere in the UI. Updating the System Application Title in JIRA Admin >> System >> General configuration does not update OAUTHCONSUMER.consumername, meaning that applinked apps will always refer to linked JIRA instances as "Your Company JIRA" in the above security contexts.

Steps to Reproduce

1. Set up a new JIRA instance, and set a custom application title in JIRA Admin >> System >> General configuration
2. Create a new application link to another app, e.g. Bitbucket Server
3. Edit the application link title to another custom name
4. Trigger the "Your Company JIRA would like read/write access to Bitbucket", e.g. by clicking on a smart commit link inside a JIRA issue to get Bitbucket to prompt the user to allow JIRA access.

Expected Results

The name given to the remote app should match the one set in the Application Title in JIRA

Actual Results

"Your Company JIRA" is always shown

Workaround

Manually update the consumername column value in OAUTHCONSUMER table in JIRA, and restart JIRA to clear any memory-mapped values. Recreate the application link, and the security dialog will now display the correct name.