Clicking username tag in Direct Message foreword navigates to the same chat

Description:

The username tag in the Direct Message Starting @username foreword message behaves incorrectly.
Clicking the username triggers a client side navigation to the same direct message route, causing the chat feed to re-render and briefly show a loading state, instead of opening any user related information.

---

Steps to reproduce:

1. Open a Direct Message with any user.
2. Scroll to the beginning of the conversation until the system message appears:
   “You have joined a new direct message with @username”.
3. Click on the @username shown in the foreword message.
4. Observe the chat view and loading behavior.

---

Expected behavior:

Clicking the @username should not trigger a navigation to the same route.
Instead of that:

• The User Info sidebar, showing the user profile OR
• The @username tag should not be clickable in this context.

Actual behavior:

Clicking the username navigates to the same Direct Message route, which causes the chat feed to re-fetch data and briefly display a loading state.

---

Server Setup Information:

• Version of Rocket.Chat Server: develop branch latest
• License Type:
• Number of Users:
• Operating System: Linux
• Deployment Method:
• Number of Running Instances:
• DB Replicaset Oplog:
• NodeJS Version: 22.16.0
• MongoDB Version:

Client Setup Information

• Desktop App or Browser Version:
• Operating System: Linux

---

Additional context

video

https://github.com/user-attachments/assets/3a3ab189-815f-4412-8221-23c57a0ab786

Relevant logs:

Start by reproducing the issue in the Direct Message foreword message and trace how the @username tag handles clicks and navigation. Confirm the current route and loading behavior, then make the interaction avoid navigating to the same direct message; done means no same-route navigation or loading state occurs when the tag is clicked.