Issue Summary

When using wiki representation while creating a page through APIs, we are unable to tag users that have colon ( their AAIDs.

Steps to Reproduce

1. Setup the API with all required info.
   • Here is an example body:

     • "body": {
           "representation": "wiki",
           "value": "h2. Postmortem Status\n\n| *Date* | 15/01/2024 |\n| *Status* |Draft |\n| *Contributors* | [~712020:d1234f04-8bc9-402d-89fb-d9be2302f5e1], [db1234f04-8bc9-402d-89fb-d9be2302f5e1]" ,
           "representation": "wiki"
         }

1. Execute the API.
2. It then creates a page as expected.
3. Now verify the tags under "Contributors"

Expected Results

• The tagged user should show up with the username for both users in the example.

Actual Results

• The user with no ":" shows up correctly.
• However, the user with ":" is displayed with the part of AAID that comes after ":".
  • For example we have this AAID in the body "712020:d1234f04-8bc9-402d-89fb-d9be2302f5e1".
  • When the page is created the part that shows up on the page is "d1234f04-8bc9-402d-89fb-d9be2302f5e1".
  • Also the hyperlink considers it to be the spacekey and tries to open such space when we click on it.
• This behaviour is being caused due to the overlap on how we call space keys with wiki. 
  • Here is the page that talks about the methods:
  • https://support.atlassian.com/confluence-cloud/docs/insert-confluence-wiki-markup/#:~:text=for%20another%20space.-,%5B~username%5D,-Link%20to%20the
  • 
• However the username is defined with ~ and that should be able to differentiate with username and spacekey.

Workaround

So far only workaround is to use storage method instead of wiki.