upcoming: [M3-7414] - Add mocks and update queries for new Parent/Child endpoints

[mjac0bs]

Description 📝

This PR adds Mock Service Worker (MSW) endpoints for all new "Parent/Child" API calls. (Updates to all existing endpoints were previously done in #9942.) These changes will enable us to mock the Parent/Child API interactions, ensuring our development remains unimpeded and independent of ongoing API changes.

Changes 🔄

• Added endpoints to the MSW for new Parent/Child endpoints.
• Updated the queries for useChildAccounts and useChildAccount to allow an unrestricted parent account to be able to reach these endpoints. (They will have child_account_access by default, but we can't check grants on an unrestricted user, which was relied upon in the initial implementation of the queries.)

Preview 📷

How to test 🧪

Prerequisites

(How to setup test environment)

• Check out this PR and add a new REACT_APP_PROXY_PAT to your .env with any token to test. We'll need to store a mock "proxy" token to log into a child account somewhere until the API returns it.
• Start the dev server: yarn dev.
• In dev tools:
  • Turn on the MSW.
  • Make sure the Parent/Child feature flag is on.

Verification steps

(How to verify changes)

• Take a look at the removed lines of code in UserMenu.tsx in the commit e129bf0.
  You will need:

  const { data: childAccounts } = useChildAccounts({});
  const { data: childAccount } = useChildAccount({ euuid: '1' });
  const {
    mutateAsync: fetchProxyToken,
  } = useCreateChildAccountPersonalAccessTokenMutation({ euuid: '1' });

  fetchProxyToken({ euuid: '1' })
      .then((data) => {
        console.log({ data });
      })

• To test the mocked queries, add the code to a component (UserMenu makes sense for our purposes) and verify in the dev console log and/or through the network request and response payload that the mocked requests to GET /account/child-accounts, GET /account/child-accounts/<euuid>, and POST /account/child-accounts/<euuid>/token are all executing and returning the expected data.

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

[mjac0bs]

This change and the change in the query below allows an unrestricted parent user (who cannot call useGrants) to access the endpoint.

[github-actions]

Coverage Report: ✅
Base Coverage: 86.51%
Current Coverage: 86.51%

[jaalah-akamai]

Changes look good

[tyler-akamai]

Verified the following returns the mocked data

• GET /account/child-accounts
• GET /account/child-accounts/<euuid>
• POST /account/child-accounts/<euuid>/token

[tyler-akamai]

LGTM, great work

[mjac0bs]

Merging this now. The only CI test failure was on rebuild-linode.spec.ts and was unrelated. (And that test passes locally.)