feat: [M3-7526] - Add setHeader to GET /profile endpoint

[tyler-akamai]

Description 📝

In order for the proxy account to access the username of the parent account, we need to use the auth token of the parent to collect the parent's profile info on behalf of the proxy account. We will have the parent account's token available to us for this use after storing it in local storage when the parent logs in as the proxy user via the "Switch Account" button.

Changes 🔄

List any change relevant to the reviewer.

• Added setHeaders to the /profile endpoint
• Added an empty object to all useProfile instances

How to test 🧪

• Add the code from the commit named use this to test PR - make sure to remove the undefined param from the useProfile call
• Make sure to add a PAT from another account to your .env file (this could be your personal account or a test account)
• Ensure both usernames are logged similar to the screenshot below
  

As an Author I have considered 🤔

Check all that apply

• 👀 Doing a self review
• ❔ Our contribution guidelines
• 🤏 Splitting feature into small PRs
• ➕ Adding a changeset
• 🧪 Providing/Improving test coverage
• 🔐 Removing all sensitive information from the code and PR description
• 🚩 Using a feature flag to protect the release
• 👣 Providing comprehensive reproduction steps
• 📑 Providing or updating our documentation
• 🕛 Scheduling a pair reviewing session
• 📱 Providing mobile support
• ♿ Providing accessibility support

[github-actions]

Coverage Report: ✅
Base Coverage: 77.77%
Current Coverage: 77.77%

[mjac0bs]

Cypress CI failures look relevant here and can be reproduced with a local run:

[jdamore-linode]

Just a heads up that the E2E test failures all seem to stem from HTTP 500 responses from the API during resource clean up and aren't caused by these changes

[mjac0bs]

Nice, I confirmed that I see another request to /profile on behalf of the account we're passing a token in for, and their username is available:

and there's our RQ query key:

Thanks for your work on this! If you get a chance to update the internal ticket based on our discussion, that would be great.

Edit: The tests that failed in CI are billing/smoke-billing-activity.spec.ts (passes locally) and account/sms-verification.spec.ts, which seems to be failing consistently locally when looking for the phone number to display after it's verified, and it doesn't. This test passed in develop, so not quite sure what's happening here.

[jaalah-akamai]

@tyler-akamai You may need to update this branch to avoid all the file noise we're seeing in Files Changed

[jaalah-akamai]

This looks good 👍