Feat: Update Session Details Information View on Pages

What does this MR do and why?

This MR DOES: This MR updates the Sessions Details page Information view (in Projects). These contain 3 new sections that go as follows:

• Identity: Session, Flow, Project, Group
• Execution: Triggered by, Started, Last updated
• Supplemental: Default model, CI Jobs

Link stylings align with merge request pages: Dark until hover, then uses blue link with underline. Also uses GlAttributeList for Sections and dt,dr,dd tags for description blocks to align with other right rail components.

This MR also removes (as we move these in MRs currently in review or merged for the Session Details headers):

• Status badge
• Triggered user

This MR DOES NOT:

• Include the collapse functionality when the page is smaller. There will be a follow up to align the rail component to behave like the merge request pages.

References

Related GitLab Work Items:

• Work Item: #609575 (closed)
• Task: #622008 (closed)
• FF Work Item: #622809

Related Merge Request Dependencies (what must be merged first):

• !251920 (merged)
• !251918 (merged)

Screenshots or screen recordings

Before	After	Screen Recording

How to set up and validate locally

For DAP/General Setup

• General DAP: https://docs.gitlab.com/development/duo_agent_platform/
• Assigning Duo to a group: https://docs.gitlab.com/development/ai_features/#run-gitlabduosetup-script
• Make sure you are in SaaS mode with export GITLAB_SIMULATE_SAAS=1 set in your env.runit file in your local gdk.
• Turn on the following feature flags (if necessary): duo_workflow, duo_workflow_in_ci, ai_flow_triggers.

Adding Sessions

1. A: If you see no Sessions, you can trigger one that displays a Pipeline/Job by going to an Issue within your Duo enabled project and clicking the Generate MR with Duo button. It should trigger a new session that you can open up.
2. B: You can also run the following query bundle exec rake "gitlab:duo_workflow:populate[50,20,1,<<YOUR_TEST_GROUP_PATH_HERE>>]" to create new agent sessions. Refresh the page. Make sure the group you are testing in has Duo assigned (see DAP setup above).

Test Session Details (The Actual Testing)

1. Make sure you are in a Duo enabled projects where Sessions permissions have been set.

Test Details Information (Project)

1. Go to the AI > Sessions on the left rail.
2. Click any Session or trigger a new one.
3. View the current session details (existing)
4. Make sure you have the feature flag: session_details_right_rail, enabled. You can use: http://gdk.test:3000/rails/features/
5. Validate changes apply to

Test Details Information Changes (Side Panel)

1. Trigger a new session. A quick easy way is to tag Duo Developer in a comment/note for Work Items or Merge Requests.
2. Go to the Side Panel on the right and open the Sessions tab (the double square icon)
3. Click the freshly generated Session.
4. Validate the Project now matches the details links and so does the Triggered user.
5. Click the i icon at the top, and validate none of the session details has changed besides the top attribute list item no longer has a top border applied.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #622008 (closed)