Update to ApolloClient@3: Verify Secure Analyzers' pages

ApolloClient is being upgraded in !55062 (merged). As part of this effort, FE team members are being asked to verify that their GraphQL-based apps still behave properly.

Verification process

• Pull !55062 (merged) locally.
• Make sure to install the NPM dependencies by running yarn.
• Navigate to the page and smoke-test the happy path for anything that triggers GraphQL queries.
  • Pay extra attention to paginated queries or any interaction that might result in the cache being mutated client-side.
• Check the page off the list if everything looks good.

Pages to be verified

• groupcomposition analysis @farias-gl
  • Dependency Scanning configuration (/:namespace/:project/-/security/configuration)
  • Container Scanning ​configuration (/:namespace/:project/-/security/configuration)
• groupdynamic analysis @djadmin @arfedoro
  • DAST configuration form (/:namespace/:project/-/security/configuration/dast)
  • DAST profiles management (/:namespace/:project/-/security/configuration/dast_scans)
  • DAST site profile form (/:namespace/:project/-/security/configuration/dast_scans/dast_site_profiles/new)
  • DAST scanner profile form (/:namespace/:project/-/security/configuration/dast_scans/dast_scanner_profiles/new)
  • On-demand scans (/:namespace/:project/-/on_demand_scans)
  • On-demand scan form (/:namespace/:project/-/on_demand_scans/new)
  • API Fuzzing ​configuration (/:namespace/:project/-/security/configuration)
  • Corpus management
• groupstatic analysis @jannik_lehmann
  • SAST configuration form (/:namespace/:project/-/security/configuration/sast)
  • IaC Scanning configuration (/:namespace/:project/-/security/configuration)

/cc @gitlab-org/secure/analyzer_frontend