Update to ApolloClient@3: Verify Threat insights 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.
  • Open the browser console to spot any warnings / errors
  • 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

Admin

• Security Dashboard (/-/security/dashboard)
• Vulnerability Report (/-/security/vulnerabilities)
• Settings (/-/security/dashboard/settings)

Group

• Security Dashboard (/groups/:group/-/security/dashboard)
• Vulnerability Report (/groups/:group/-/security/vulnerabilities)

Project

• Security Dashboard (/:namespace/:project/-/security/dashboard)
• Vulnerability Report (/:namespace/:project/-/security/vulnerability_report)
• Vulnerability Details (/:namespace/:project/-/security/vulnerabilities/257)
• Pipeline wiget (/:namespace/:project/-/pipelines/97/security)
• MR widget (/:namespace/:project/-/merge_requests/3)

Container Security

• The below pages (@aturinske @dftian - as domain experts, please fill out this section and verify 🙇 )
  • Threat Monitoring Alerts
  • Policies (/:namespace/:project/-/security/policies)
  • Policies New (/:namespace/:project/-/security/policies/new)
  • Policies Edit (/:namespace/:project/-/security/policies/:policy-name/edit?environment_id=44&type=scan_execution_policy)
  • Policies Delete (/:namespace/:project/-/security/policies/:policy-name/edit?environment_id=44&type=scan_execution_policy)
  • Cluster Agent Security (`/:namespace/:project/-/cluster_agents/:agent-name?tab=security)

/cc @gitlab-org/secure/threat-insights-frontend-team