feat: expand the application data exposed on submission_services_summary

[Mike-Heneghan]

What

• Spun out of draft PR: feat: show submitted applications for a flow in the flow settings  #2867
• Add submission_services_summary tracking
• Expand the application data exposed in the view
• Adding columns:
  • payment_request
  • payment_status
  • bops_applications
  • uniform_applications
  • email_applications
• Each summarising related records as an array of objects with pertinent data

Why

• As per: feat: show submitted applications for a flow in the flow settings  #2867 (comment)
• The submission_services_summary can be expanded to expose the requested data and isn't PII
• Council officers need to be able to connect the various ids, payments and submissions related to applications

[github-actions]

🤖 Hasura Change Summary compared a subset of table metadata including permissions:

Tracked Tables (1)

• public.submission_services_summary permissions:

  	insert	select	update	delete
  platformAdmin		➕
  teamEditor		➕

  34 added column permissions

  	insert	select	update
  platformAdmin		➕ bops_applications ➕ created_at ➕ email_applications ➕ number_times_resumed ➕ payment_requests ➕ payment_status ➕ sent_to_bops ➕ sent_to_email ➕ sent_to_uniform ➕ service_slug ➕ session_id ➕ session_length_days ➕ submitted_at ➕ team_slug ➕ uniform_applications ➕ user_clicked_save ➕ user_invited_to_pay
  teamEditor

[github-actions]

Removed vultr server and associated DNS entries

[jessicamcinchak]

Looks good to me! Nice job incorporating the new many-to-one array columns while maintaining the rest of the previous structure so analytics shouldn't break 👍