[no-Jira] Upgrade prettier to v3

[canac]

Description

I was trying to use the newish satisfies TypeScript operator on another PR and noticed that it messed up prettier. It appears to be because prettier wasn't new enough. This PR simply upgrades to prettier 3 and removes the trailingComma configuration because it defaults to all now. It seems that the main breaking change is how it formats nested ternaries.

Checklist:

• I have given my PR a title with the format "MPDX-(JIRA#) (summary sentence max 80 chars)"
• I have applied the appropriate labels. (Add the label "On Staging" to get the branch automatically merged into staging.)
• I have requested a review from another person on the project

[github-actions]

Preview branch generated at https://upgrade-prettier.d3dytjb8adxkk5.amplifyapp.com

[github-actions]

Bundle sizes [mpdx-react]

Compared against ccd5ff7

No significant changes found

[dr-bizz]

The code looks good. I have a question with updating the tests, but will approve as it's not blocking.

[dr-bizz]

I assume this is related to the work being done on staging?

[canac]

Upgrading prettier changed how it was formatting the GraphQL operations. The gql query definitions in the generated files like this one:

export const ContactFiltersDocument = gql`
  query ContactFilters($accountListId: ID!) {
    accountList(id: $accountListId) {
      id
      contactFilterGroups {
        ...FilterPanelGroup
      }
      partnerGivingAnalysisFilterGroups {
        ...FilterPanelGroup
      }
    }
    userOptions {
      ...UserOption
    }
  }
  ${FilterPanelGroupFragmentDoc}
  ${UserOptionFragmentDoc}
`;

I believe that our GraphQL mocking library seeds the random number generator with a hash of the GraphQL operation. So even if just whitespace changes, it will generate different values for fields not explicitly mocked. A few tests were dependent on those random values and broke when they changed.