fix: use orgAwareUsername in troubleshooter getSchedule request

[hariombalhara]

What does this PR do?

Fixes the troubleshooter's getSchedule request to use orgAwareUsername instead of username when fetching schedule data.

In organization contexts, users have different usernames per organization (via Profiles). The troubleshooter was using session?.user.username which returns the base username, but the getSchedule endpoint expects the org-aware username to properly resolve the user's schedule within the organization context. This aligns the troubleshooter behavior with how the booking page handles the same request.

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A - no documentation changes needed.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

1. Set up a user within an organization that has a different org username than their base username
2. Navigate to the troubleshooter page
3. Verify that the schedule loads correctly and shows the user's availability
4. Compare behavior with the booking page to ensure consistency

Human Review Checklist

• Verify orgAwareUsername is available in all contexts where username was previously used (org and non-org users)
• Confirm this matches how the booking page handles username in getSchedule requests

---

Link to Devin run: https://app.devin.ai/sessions/5661869d6af3401c9ba6a099575673a9
Requested by: @hariombalhara

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[cubic-dev-ai]

No issues found across 1 file