Enhancements production ready screens

Summary

Problem: What is the pain point? (e.g., "Users cannot filter results by date.")
Userflow to request a connection to the production environment of SURF Access has had an overhaul to make it more clear to the end user.

Value: Why should we build this? (e.g., "Improves data accessibility for
power users.")
Improves user experience and selfservice and put less strain on the service desk

Proposed Solution

• Action: Describe the logic or flow change.

• Design: Prototype: https://www.figma.com/proto/81StIVqfOKfwhWVjx7Ew81/SURF-Access?node-id=12988-48446&viewport=142%2C-519%2C0.66&t=eofJhVN8a2ZkNIqC-8&scaling=contain&content-scaling=responsive&page-id=9684%3A52896&hide-ui=1
  Designs: https://www.figma.com/design/81StIVqfOKfwhWVjx7Ew81/SURF-Access?node-id=13265-69876&t=0Tx6d9GpdVd5KZ93-1

Developer Checklist

To be completed by the developer during implementation.

• Add required changes and feature flags config files
• Create and document database changes and migrations
• Create and document API changes and migrations
• check for backwards compatibility
• Updated CHANGELOG and other documentation where needed

Testing and QA

Describe how to verify and test this change.

Test Environment and Setup

1. Point to [URL/Branch]
2. Use account with [Role/Permissions]

Test Checklist

Note that "Note that email is received by the applicant after Jira issue is resolved" depends on https://github.com/OpenConext/OpenConext-access/issues/256

• Publish a connection to the production environment (setting: via app catalogue and direct without notification)
• Note that the user is notified via app that ticket has been created and change request has been requested
• Note that a manage change request has been created
• Note that the field coin:dashboard_connect_option is set correctly in Manage
• Note that a Jira ticket has been created
• Accept the manage change request (under 'staging', or look for the entity and see under tab 'requests')
• Note that after a refresh of the app detail page (/allConnections/) connection is live
• Note that a link to the connection in the catalogue is present
• Resolve Jira ticket
• Note that email is received by the applicant

• Publish a connection to the production environment (setting: via app catalogue and direct with notification)
• Note that the user is notified via app that ticket has been created and change request has been requested
• Note that a manage change request has been created
• Note that the field coin:dashboard_connect_option is set correctly in Manage
• Note that a Jira ticket has been created
• Accept the manage change request (under 'staging', or look for the entity and see under tab 'requests')
• Note that after a refresh of the app detail page (/allConnections/) connection is live
• Note that a link to the connection in the catalogue is present
• Resolve Jira ticket
• Note that email is received by the applicant

• Publish a connection to the production environment (setting: via app catalogue and 'request required')
• Note that the user is notified via app that ticket has been created and change request has been requested
• Note that a manage change request has been created
• Note that the field coin:dashboard_connect_option is set correctly in Manage
• Note that a Jira ticket has been created
• Accept the manage change request (under 'staging', or look for the entity and see under tab 'requests')
• Note that after a refresh of the app detail page (/allConnections/) connection is live
• Note that a link to the connection in the catalogue is present
• Resolve Jira ticket
• Note that email is received by the applicant

• Publish a connection to the production environment (setting: via 'direct link')
• Note that the user is notified via app that ticket has been created and change request has been requested
• Note that a manage change request has been created
• Note that the field coin:ss:hidden is set correctly in Manage
• Note that a Jira ticket has been created
• Accept the manage change request (under 'staging', or look for the entity and see under tab 'requests')
• Note that after a refresh of the app detail page (/allConnections/) connection is live
• Note that a link to the connection in the catalogue is present
• Resolve Jira ticket
• Note that email is received by the applicant