SEC-6831 Fix autolink dependency path

[wiggin77]

Summary

When the autolink plugin was moved from mattermost org to mattermost-community the module path was not updated for this Jira plugin. This PR resolves it.

This issue was discovered via automated scan.

Ticket Link

https://mattermost.atlassian.net/browse/SEC-6831

[wiggin77]

@AayushChaudhary0001 this changes the version of autolink used in the Jira plugin. We'll need a test to make sure link resolution still works. This can be tested for next release, or tested before merge at your discretion.

[wiggin77]

@raghavaggarwal2308 we have a bunch of PRs failing CI CodeQL step. Can you look into this and unblock the PRs?

[raghavaggarwal2308]

@wiggin77 Sure, we are looking into it

[AayushChaudhary0001]

This PR has been tested for Jira plugin, and it was found not working. On pasting the link of any desired ticket from Jira, it was presented to the user as original link and not the ticket ID as a link.

[raghavaggarwal2308]

@wiggin77

• We looked into the above issue and found out the code implemented for setting up autolinks is for Jira cloud instance (Using JWT token for auth) only and we moved to oauth2 recently.
• To make this work we will have to update that logic to use cloudOauth instance.

Should we log an issue for the above and fix it?

[wiggin77]

/update-branch

[wiggin77]

Should we log an issue for the above and fix it?

Yes please @raghavaggarwal2308

[wiggin77]

Should we log an issue for the above and fix it?

Yes please @raghavaggarwal2308

@raghavaggarwal2308 also can we get a unit test to detect this issue so it can be caught before manual testing?

[raghavaggarwal2308]

@wiggin77 Sure, we will add the unit testcases